overlay/014: correct comment relating to workdir reuse

Clarification: EBUSY is what you get when trying to use the same
upperdir/workdir with two different *concurent* overlayfs mounts.
The EBUSY case is independent of the inodes index feature.

This is not the case in this test, but rather the case of trying to
reuse the same workdir with different upper dirs on *subsequent*
overlayfs mounts.

Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Reviewed-by: Eryu Guan <eguan@redhat.com>
Signed-off-by: Eryu Guan <eguan@redhat.com>
This commit is contained in:
Amir Goldstein
2017-09-19 14:39:43 +03:00
committed by Eryu Guan
parent e04905eba7
commit 5052c432b5
+3 -4
View File
@@ -63,10 +63,9 @@ lowerdir1=$OVL_BASE_SCRATCH_MNT/lower1
lowerdir2=$OVL_BASE_SCRATCH_MNT/lower2
upperdir=$OVL_BASE_SCRATCH_MNT/upper
workdir=$OVL_BASE_SCRATCH_MNT/workdir
# When overlay inode index feature is enabled, using an upper layer path and/or
# a workdir path that are already used by another overlay mount is not allowed
# and will fail with EBUSY, so create another workdir for the second overlay
# mount
# When overlay inode index feature is enabled, a workdir cannot be reused
# with a different upperdir. workdir2 in this test is used as the workdir
# when lowerdir2 is used as the upperdir.
workdir2=$OVL_BASE_SCRATCH_MNT/workdir2
mkdir -p $lowerdir1 $lowerdir2 $upperdir $workdir $workdir2
mkdir -p $lowerdir1/testdir/d