Lines Matching refs:directory
24 non-directory objects may report an st_dev from the lower filesystem or
27 over the lifetime of a non-directory object. Many applications and
59 It would be more correct to refer to an upper and lower 'directory
61 directory trees to be in the same filesystem and there is no
78 upper and lower filesystems and refers to a non-directory in either,
82 Where both upper and lower objects are directories, a merged directory
86 "upperdir" are combined into a merged directory:
91 The "workdir" needs to be an empty directory on the same filesystem
94 Then whenever a lookup is requested in such a merged directory, the
95 lookup is performed in each actual directory and the combined result
98 directory is created, otherwise only one is stored: the upper if it
103 directory only. These attributes of the lower directory are hidden.
114 When a whiteout is found in the upper level of a merged directory, any
118 A directory is made opaque by setting the xattr "trusted.overlay.opaque"
119 to "y". Where the upper filesystem contains an opaque directory, any
120 directory in the lower filesystem with the same name is ignored.
125 When a 'readdir' request is made on a merged directory, the upper and
130 directory is opened and read by two processes at the same time, they
132 directory (offset 0) followed by a readdir will cause the cache to be
135 This means that changes to the merged directory do not appear while a
136 directory is being read. This is unlikely to be noticed by many
142 - read part of a directory
143 - remember an offset, and close the directory
144 - re-open the directory some time later
149 directory.
152 underlying directory (upper or lower).
157 When renaming a directory that is on the lower layer or merged (i.e. the
158 directory was not created on the upper layer to start with) overlayfs can
162 move a file or directory across filesystem boundaries. Hence
164 recursively copies the directory tree). This is the default behavior.
166 2. If the "redirect_dir" feature is enabled, then the directory will be
169 root of the overlay. Finally the directory is moved to the new
206 When the NFS export feature is enabled, every copied up directory is
208 upper directory is stored in a "trusted.overlay.upper" extended attribute
209 on the index entry. On lookup of a merged directory, if the upper
210 directory does not match the file handle stores in the index, that is an
212 lower directory. In that case, lookup returns an error and warns about
235 The copy_up process first makes sure that the containing directory
253 separator character between the directory names. For example:
316 handle of the lower layer root directory, along with the UUID of the lower
318 attribute on the upper layer root directory. On subsequent mount attempts,
319 the lower root directory file handle and lower filesystem UUID are compared
320 to the stored origin in upper root directory. On failure to verify the
331 directory tree on the same or different underlying filesystem, and even
359 If this feature is disabled, then rename(2) on a lower or merged directory
383 overlay filesystem and the value of st_ino for directory objects may not be
406 When the NFS export feature is enabled, a lookup of a merged directory,
407 that found a lower directory at the lookup path or at the path pointed
409 that the found lower directory file handle and lower filesystem UUID
411 found lower directory does not match the stored origin, that directory
412 will not be merged with the upper directory.
423 entry is created under the index directory. The index entry name is the
425 non-directory object, the index entry is a hard link to the upper inode.
426 For a directory object, the index entry has an extended attribute
428 directory inode.
450 3. For a lower file handle, lookup the handle in index directory by name.
453 5. For a non-directory, instantiate a disconnected overlay dentry from the
455 6. For a directory, use the connected underlying decoded dentry, path type
458 Decoding a non-directory file handle may return a disconnected dentry.
463 directory may have a "redirect" to lower directory. Because middle layer
465 "redirect" origin directory, cannot be used to find the middle or upper
466 layer directory. Similarly, a lower file handle that was encoded from a
467 descendant of the "redirect" origin directory, cannot be used to
475 The overlay filesystem does not support non-directory connectable file
479 When the NFS export feature is enabled, all directory index entries are