Lines Matching refs:upper

25 upper filesystem that is providing the object.  Similarly st_ino will
33 An overlay filesystem combines two filesystems - an 'upper' filesystem
35 object in the 'upper' filesystem is visible while the object in the
37 merged with the 'upper' object.
39 It would be more correct to refer to an upper and lower 'directory
42 requirement that the root of a filesystem be given for either upper or
47 overlayfs.  The upper filesystem will normally be writable and if it
58 upper and lower filesystems and refers to a non-directory in either,
59 then the lower object is hidden - the name refers only to the upper
62 Where both upper and lower objects are directories, a merged directory
68   mount -t overlay overlay -olowerdir=/lower,upperdir=/upper,\
78 directory is created, otherwise only one is stored: the upper if it
82 such as metadata and extended attributes are reported for the upper
89 filesystem, an overlay filesystem needs to record in the upper filesystem
94 When a whiteout is found in the upper level of a merged directory, any
99 to "y".  Where the upper filesystem contains an opaque directory, any
105 When a 'readdir' request is made on a merged directory, the upper and
107 obvious way (upper is read first, then lower - entries that already
131 underlying directory (upper or lower).
138 files etc.) are presented either from the upper or lower filesystem as
142 to the upper filesystem (copy_up).  Note that creating a hard-link
150 exists in the upper filesystem - creating it and any parents as
153 data is copied from the lower to the upper filesystem.  Finally any
157 provides direct access to the newly created file in the upper
210 the upper or the lower trees.