Log Message:
-----------
* run-tests: When using loop devices and nfsv3, sometimes some of
the lower branches cannot be unmounted with an EBUSY. But if you
wait a little longer for pdflush to run, or run /bin/sync
manually, then you can mount those lower branches. This is
probably some sort of a race between the loop device driver and
NFSv3. We can work around it if we mount all nfs partitions with
"-o sync", or run sync by hand here.
* t-truncate-all.sh: bugfix, discovered when trying NFS for the
lower branches. Check if branch 2 supports chatter, not top-level
directory.
Tags:
----
LKML-branch
Modified Files:
--------------
unionfs/regression-2.0:
ChangeLog (r1.1.2.27 -> r1.1.2.28)
run-tests (r1.1.2.13 -> r1.1.2.14)
t-truncate-all.sh (r1.1.2.2 -> r1.1.2.3)
Revision Data
-------------
Index: t-truncate-all.sh
===================================================================
RCS file: /home/cvs/unionfs/unionfs/regression-2.0/Attic/t-truncate-all.sh,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -Lregression-2.0/t-truncate-all.sh -Lregression-2.0/t-truncate-all.sh -u
-d -b -B -p -r1.1.2.2 -r1.1.2.3
--- regression-2.0/t-truncate-all.sh
+++ regression-2.0/t-truncate-all.sh
@@ -51,7 +51,7 @@ dd if=/dev/zero of=$LOWER_DIR2/d1/d2/d3/
dd if=/dev/zero of=$LOWER_DIR2/d1/d2/d3/d4/f bs=4000 count=2 2>/dev/null
-if havechattr $TOP_LOWER_DIR ; then
+if havechattr $LOWER_DIR2 ; then
CHATTR=1
chattr +i $LOWER_DIR2/d1/d2/d3/d4/f
fi
Index: ChangeLog
===================================================================
RCS file: /home/cvs/unionfs/unionfs/regression-2.0/Attic/ChangeLog,v
retrieving revision 1.1.2.27
retrieving revision 1.1.2.28
diff -Lregression-2.0/ChangeLog -Lregression-2.0/ChangeLog -u -d -b -B -p
-r1.1.2.27 -r1.1.2.28
--- regression-2.0/ChangeLog
+++ regression-2.0/ChangeLog
@@ -1,5 +1,17 @@
2007-05-28 Erez Zadok <[EMAIL PROTECTED]>
+ * run-tests: When using loop devices and nfsv3, sometimes some of
+ the lower branches cannot be unmounted with an EBUSY. But if you
+ wait a little longer for pdflush to run, or run /bin/sync
+ manually, then you can mount those lower branches. This is
+ probably some sort of a race between the loop device driver and
+ NFSv3. We can work around it if we mount all nfs partitions with
+ "-o sync", or run sync by hand here.
+
+ * t-truncate-all.sh: bugfix, discovered when trying NFS for the
+ lower branches. Check if branch 2 supports chatter, not top-level
+ directory.
+
* run-tests: don't print annoying delay messages more than once.
2007-05-25 Erez Zadok <[EMAIL PROTECTED]>
Index: run-tests
===================================================================
RCS file: /home/cvs/unionfs/unionfs/regression-2.0/Attic/run-tests,v
retrieving revision 1.1.2.13
retrieving revision 1.1.2.14
diff -Lregression-2.0/run-tests -Lregression-2.0/run-tests -u -d -b -B -p
-r1.1.2.13 -r1.1.2.14
--- regression-2.0/run-tests
+++ regression-2.0/run-tests
@@ -200,6 +200,14 @@ do
# run actual test and abort on error (test script tries to umount unionfs)
runcmd bash $t
+ # When using loop devices and nfsv3, sometimes some of the lower branches
+ # cannot be unmounted with an EBUSY. But if you wait a little longer for
+ # pdflush to run, or run /bin/sync manually, then you can mount those
+ # lower branches. This is probably some sort of a race between the loop
+ # device driver and NFSv3. We can work around it if we mount all nfs
+ # partitions with "-o sync", or run sync by hand here.
+ runcmd sync
+
# try to unmount lower file systems (check if we leak anything)
for i in 0 1 2 3 ; do
do_umount $i $(eval echo \$DEV$i) $(eval echo \$FS$i)
_______________________________________________
unionfs-cvs mailing list: http://unionfs.filesystems.org/
[email protected]
http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs-cvs
