Lines Matching full:directories

25 While directories will report an st_dev from the overlay-filesystem,
89 'lower' filesystem is either hidden or, in the case of directories,
109 Directories
112 Overlaying mainly involves directories.  If a given name appears in both
117 Where both upper and lower objects are directories, a merged directory
120 At mount time, the two directories given as mount options "lowerdir" and
132 actual lookups find directories, both are stored and a merged
136 Only the lists of names from directories are merged.  Other content
140 whiteouts and opaque directories
146 directories (non-directories are always opaque).
170 lower directories are each read and the name lists merged in the
183 seek offsets are assigned sequentially when the directories are read.
195 Readdir on directories that are not merged is simply handled by the
198 renaming directories
254 indication that multiple upper directories may be redirected to the same
263 Non-directories
266 Objects that are not directories (files, symlinks, device-special
361 The specified lower directories will be stacked beginning from the
399 Do not use metacopy=on with untrusted upper/lower directories. Otherwise
439 merged overlayfs directories and the metadata and st_ino/st_dev of files
495 changes in the overlayfs directories in use. But, with additional care
500 directories are specified as "Data-only", then they can only supply
580 "overlay.opaque" xattr set to "x" (see `whiteouts and opaque directories`_).
731 directories that cannot be decoded from a lower file handle, these
732 directories are copied up on encode and encoded as an upper file handle.
751 is changed. This is only applicable if all lower/upper/work directories are on
801 indicator that user should throw away upper and work directories and create