Lines Matching full:mount

49 symbolic links and mount traps.  Mount traps are directories with
54 mount traps are created with `mkdir`.  The determination of whether a
55 directory should be a mount trap or not is quite _ad hoc_, largely for
57 *direct*/*indirect*/*offset* mount options, and the *maxproto* mount option.
59 If neither the *direct* or *offset* mount options are given (so the
60 mount is considered to be *indirect*), then the root directory is
61 always a regular directory, otherwise it is a mount trap when it is
64 directory is a mount trap only if the filesystem is mounted *direct*
67 Directories created in the root directory are mount traps only if the
70 Directories further down the tree depend on the *maxproto* mount
73 tree are ever mount traps, they are always regular directories.  When
74 the *maxproto* is four (or three), these directories are mount traps
77 So: non-empty (i.e. non-leaf) directories are never mount traps. Empty
78 directories are sometimes mount traps, and sometimes not depending on
80 and whether the mount was *indirect* or not.
82 Mount Traps
85 A core element of the implementation of autofs is the Mount Traps
94 (potentially) a mount trap.  Any access to this directory beyond a
102 automount daemon asking it to find and mount the filesystem.  The
105 mount has already happened.  The VFS doesn't try to mount anything but
106 follows down the mount that is already there.
108 This functionality is sufficient for some users of mount traps such
112 automount daemon would not be able to mount a filesystem on the 'trap'
137    causing the directory not be a mount trap after all.
140    lookup is the automount daemon and that the mount has been
143    caught in the mount trap.
147    be managed by the same daemon.  For the daemon to be able to mount
150    the automount daemon.  It must only return it when a mount has
154    mount trap, either because it is a symbolic link or because it is
162    - -ENOENT if the automount daemon failed to mount anything,
179 To determine if a mount-trap is safe for RCU-walk mode it calls
185 reason that it might not be is if an expiry of the mount is
227 it was before the mount or creation, so that any access of the name
228 will trigger normal auto-mount processing.  In particlar, `rmdir` and
234 directories.  As lower-level directories are never mount traps, other
250 using an `ioctl` as discussed later.  For a *direct* mount, autofs
251 considers if the entire mount-tree can be unmounted or not.  For an
252 *indirect* mount, autofs considers each of the names in the top level
312 be passed using the 'fd=' mount option.  autofs will write
418 document `autofs-mount-control.txt`, and are summarized briefly here.
473     the UID and GID of the process which triggered that mount.
493 As mentioned, an autofs mount can enter "catatonic" mode.  This
502 be treated in the same way as if they came from the daemon, so mount
522 > `mount --make-shared /autofs/mount/point`
524 The automount daemon is only able to manage a single mount location for