Lines Matching refs:upper

24 upper filesystem that is providing the object.  Similarly st_ino will
32 An overlay filesystem combines two filesystems - an 'upper' filesystem
34 object in the 'upper' filesystem is visible while the object in the
36 merged with the 'upper' object.
38 It would be more correct to refer to an upper and lower 'directory
41 requirement that the root of a filesystem be given for either upper or
46 overlayfs.  The upper filesystem will normally be writable and if it
57 upper and lower filesystems and refers to a non-directory in either,
58 then the lower object is hidden - the name refers only to the upper
61 Where both upper and lower objects are directories, a merged directory
67   mount -t overlay overlay -olowerdir=/lower,upperdir=/upper,\
77 directory is created, otherwise only one is stored: the upper if it
81 such as metadata and extended attributes are reported for the upper
88 filesystem, an overlay filesystem needs to record in the upper filesystem
93 When a whiteout is found in the upper level of a merged directory, any
98 to "y".  Where the upper filesystem contains an opaque directory, any
104 When a 'readdir' request is made on a merged directory, the upper and
106 obvious way (upper is read first, then lower - entries that already
130 underlying directory (upper or lower).
137 files etc.) are presented either from the upper or lower filesystem as
141 to the upper filesystem (copy_up).  Note that creating a hard-link
149 exists in the upper filesystem - creating it and any parents as
152 data is copied from the lower to the upper filesystem.  Finally any
156 provides direct access to the newly created file in the upper
209 the upper or the lower trees.