Lines Matching refs:lower

24 non-directory objects may report an st_dev from the lower filesystem or
54 and a 'lower' filesystem.  When a name exists in both filesystems, the
56 'lower' filesystem is either hidden or, in the case of directories,
59 It would be more correct to refer to an upper and lower 'directory
63 lower.
65 The lower filesystem can be any filesystem supported by Linux and does
66 not need to be writable.  The lower filesystem can even be another
78 upper and lower filesystems and refers to a non-directory in either,
79 then the lower object is hidden - the name refers only to the upper
82 Where both upper and lower objects are directories, a merged directory
88   mount -t overlay overlay -olowerdir=/lower,upperdir=/upper,\
99 exists, else the lower.
103 directory only.  These attributes of the lower directory are hidden.
108 In order to support rm and rmdir without changing the lower
115 matching name in the lower level is ignored, and the whiteout itself
120 directory in the lower filesystem with the same name is ignored.
126 lower directories are each read and the name lists merged in the
127 obvious way (upper is read first, then lower - entries that already
152 underlying directory (upper or lower).
157 When renaming a directory that is on the lower layer or merged (i.e. the
207 indexed by the file handle of the lower inode and a file handle of the
212 lower directory.  In that case, lookup returns an error and warns about
215 Because lower layer redirects cannot be verified with the index, enabling
224 files etc.) are presented either from the upper or lower filesystem as
225 appropriate.  When a file in the lower filesystem is accessed in a way
227 some metadata etc., the file is first copied from the lower filesystem
239 data is copied from the lower to the upper filesystem.  Finally any
249 Multiple lower layers
252 Multiple lower layers can now be given using the the colon (":") as a
260 The specified lower directories will be stacked beginning from the
282 Do not use metacopy=on with untrusted upper/lower directories. Otherwise
284 appropriate REDIRECT and METACOPY xattrs, and gain access to file on lower
293 a very common practice.  An overlay mount may use the same lower layer
294 path as another overlay mount and it may use a lower layer path that is
295 beneath or above the path of another overlay lower layer path.
306 different lower layer path, is allowed, unless the "inodes index" feature
310 handle of the lower layer root directory, along with the UUID of the lower
313 the lower root directory file handle and lower filesystem UUID are compared
315 lower root origin, mount will fail with ESTALE.  An overlayfs mount with
316 "inodes index" enabled will fail with EOPNOTSUPP if the lower filesystem
317 does not support NFS export, lower filesystem does not have a valid UUID or
321 mount time. So if same upper is mounted with different set of lower, mount
327 the copied layers will fail the verification of the lower root file handle.
341 If this feature is disabled, then rename(2) on a lower or merged directory
373 the upper or the lower trees.
381 behavior on offline changes of the underlying lower layer is different
384 On every copy_up, an NFS file handle of the lower inode, along with the
385 UUID of the lower filesystem, are encoded and stored in an extended
389 that found a lower directory at the lookup path or at the path pointed
391 that the found lower directory file handle and lower filesystem UUID
393 found lower directory does not match the stored origin, that directory
404 With the "nfs_export" feature, on copy_up of any lower object, an index
415 1. For a non-upper object, encode a lower file handle from lower inode
416 2. For an indexed object, encode a lower file handle from copy_up origin
421  - Header including path type information (e.g. lower/upper)
432 3. For a lower file handle, lookup the handle in index directory by name.
444 When overlay filesystem has multiple lower layers, a middle layer
445 directory may have a "redirect" to lower directory.  Because middle layer
446 "redirects" are not indexed, a lower file handle that was encoded from the
448 layer directory.  Similarly, a lower file handle that was encoded from a
451 directories that cannot be decoded from a lower file handle, these