summaryrefslogtreecommitdiff
path: root/Documentation/filesystems
diff options
context:
space:
mode:
authorAmir Goldstein <amir73il@gmail.com>2016-12-08 10:49:51 +0300
committerMiklos Szeredi <mszeredi@redhat.com>2016-12-16 13:02:58 +0300
commitc3c8699664800a68600f1988302173067eaeaffa (patch)
tree7c4e52332894184ecc4abda9ef51ece9e9103af4 /Documentation/filesystems
parent313684c48cc0e450ab303e1f82130ee2d0b50274 (diff)
downloadlinux-c3c8699664800a68600f1988302173067eaeaffa.tar.xz
ovl: fix reStructuredText syntax errors in documentation
- Fix broken long line block quote - Fix missing newline before bullets list - Use correct numbered list syntax Signed-off-by: Amir Goldstein <amir73il@gmail.com> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
Diffstat (limited to 'Documentation/filesystems')
-rw-r--r--Documentation/filesystems/overlayfs.txt7
1 files changed, 4 insertions, 3 deletions
diff --git a/Documentation/filesystems/overlayfs.txt b/Documentation/filesystems/overlayfs.txt
index fb6f3070c6fe..634d03e20c2d 100644
--- a/Documentation/filesystems/overlayfs.txt
+++ b/Documentation/filesystems/overlayfs.txt
@@ -66,7 +66,7 @@ At mount time, the two directories given as mount options "lowerdir" and
"upperdir" are combined into a merged directory:
mount -t overlay overlay -olowerdir=/lower,upperdir=/upper,\
-workdir=/work /merged
+ workdir=/work /merged
The "workdir" needs to be an empty directory on the same filesystem
as upperdir.
@@ -118,6 +118,7 @@ programs.
seek offsets are assigned sequentially when the directories are read.
Thus if
+
- read part of a directory
- remember an offset, and close the directory
- re-open the directory some time later
@@ -137,12 +138,12 @@ When renaming a directory that is on the lower layer or merged (i.e. the
directory was not created on the upper layer to start with) overlayfs can
handle it in two different ways:
-1) return EXDEV error: this error is returned by rename(2) when trying to
+1. return EXDEV error: this error is returned by rename(2) when trying to
move a file or directory across filesystem boundaries. Hence
applications are usually prepared to hande this error (mv(1) for example
recursively copies the directory tree). This is the default behavior.
-2) If the "redirect_dir" feature is enabled, then the directory will be
+2. If the "redirect_dir" feature is enabled, then the directory will be
copied up (but not the contents). Then the "trusted.overlay.redirect"
extended attribute is set to the path of the original location from the
root of the overlay. Finally the directory is moved to the new