diff options
| author | Miklos Szeredi <mszeredi@redhat.com> | 2020-11-12 11:31:55 +0100 |
|---|---|---|
| committer | Miklos Szeredi <mszeredi@redhat.com> | 2020-11-12 11:31:55 +0100 |
| commit | 58afaf5d605f091abf7491774e34fa29d4a1994c (patch) | |
| tree | 0012d0a4e668d469db013f5a8829376f771d20a2 /Documentation/filesystems/overlayfs.rst | |
| parent | 5830fb6b54f7167cc7c9d43612eb01c24312c7ca (diff) | |
| download | linux-rpi-58afaf5d605f091abf7491774e34fa29d4a1994c.tar.gz linux-rpi-58afaf5d605f091abf7491774e34fa29d4a1994c.tar.bz2 linux-rpi-58afaf5d605f091abf7491774e34fa29d4a1994c.zip | |
ovl: doc clarification
Documentation says "The lower filesystem can be any filesystem supported by
Linux". However, this is not the case, as Linux supports vfat and vfat
doesn't work as a lower filesystem
Reported-by: nerdopolis <bluescreen_avenger@verizon.net>
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Diffstat (limited to 'Documentation/filesystems/overlayfs.rst')
| -rw-r--r-- | Documentation/filesystems/overlayfs.rst | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/Documentation/filesystems/overlayfs.rst b/Documentation/filesystems/overlayfs.rst index a3e588dc8437..1ef4ef38b542 100644 --- a/Documentation/filesystems/overlayfs.rst +++ b/Documentation/filesystems/overlayfs.rst @@ -97,11 +97,13 @@ directory trees to be in the same filesystem and there is no requirement that the root of a filesystem be given for either upper or lower. -The lower filesystem can be any filesystem supported by Linux and does -not need to be writable. The lower filesystem can even be another -overlayfs. The upper filesystem will normally be writable and if it -is it must support the creation of trusted.* extended attributes, and -must provide valid d_type in readdir responses, so NFS is not suitable. +A wide range of filesystems supported by Linux can be the lower filesystem, +but not all filesystems that are mountable by Linux have the features +needed for OverlayFS to work. The lower filesystem does not need to be +writable. The lower filesystem can even be another overlayfs. The upper +filesystem will normally be writable and if it is it must support the +creation of trusted.* extended attributes, and must provide valid d_type in +readdir responses, so NFS is not suitable. A read-only overlay of two read-only filesystems may use any filesystem type. |