head	1.5;
access;
symbols
	UNIONFS-1_4:1.5
	LKML-branch:1.5.0.10
	LKML:1.5
	UNIONFS-1_3-branch:1.5.0.8
	UNIONFS-1_3:1.5
	UNIONFS-1_2:1.5
	UNIONFS-1_2-branch:1.5.0.6
	UNIONFS-1_2-branchpoint:1.5
	UNIONFS_branchman:1.5
	branchman:1.5.0.4
	UNIONFS-1_1_4:1.4.4.1
	UNIONFS-1_1-patches:1.4.0.4
	UNIONFS-1_1_3:1.4
	crc-submitted-to-ols2006:1.5
	remount:1.5.0.2
	UNIONFS-1_1_2:1.4
	BEFORE_MOUNTPOINT_CROSSING:1.4
	UNIONFS-1_1_1:1.4
	UNIONFS_PRE_1_1_1:1.4
	UNIONFS-1_1:1.4
	UNIONFS_PRE_1_1:1.4.0.2
	UNIONFS-1_0_14:1.4
	UNIONFS-1_0_13:1.2
	submitted-to-tos-2005:1.1
	UNIONFS-1_0_4:1.1;
locks; strict;
comment	@# @;


1.5
date	2006.03.03.22.24.13;	author dquigley;	state Exp;
branches;
next	1.4;

1.4
date	2005.08.15.13.11.28;	author cwright;	state Exp;
branches
	1.4.4.1;
next	1.3;

1.3
date	2005.08.12.17.40.50;	author arunmk;	state Exp;
branches;
next	1.2;

1.2
date	2005.07.19.17.32.38;	author cwright;	state Exp;
branches;
next	1.1;

1.1
date	2004.12.29.15.38.34;	author cwright;	state Exp;
branches;
next	;

1.4.4.1
date	2006.04.11.20.02.15;	author jsipek;	state Exp;
branches;
next	;


desc
@@


1.5
log
@Added check to see if its necessary to run the delete_all tests
@
text
@EXT2/3 Tests
------------
The current regression suite assumes that it can create branches in /n/lower,
and then mount them on /mnt/unionfs (the latter can be changed in scaffold).
To run the tests, first insert the unionfs module, then run one (or more) of
the shell scripts.

To run all of the tests:
for x in *.sh ; do sh $x ; done

The tests normally produce no output except "OK", "[rw]", and "[ro]" if you see
output, then there are problems.  The two most common type of outputs are
error messages from commands, or output from diff, which indicates that Unionfs
did some other lower-level operation than was expected.  The diff lines will
contain a file type (e.g., "f" for files or "d" for directories), and then a
lower-level name that shouldn't appear, or does appear.

NFS Tests
---------
The procedure is similar to the above, except that the following variables are
to be exported before running the tests:

export NFS=1
export LOWER_DIR=/dhcp/nfs # This an NFS directory to test Unionfs on

delete=all Tests
---------
The procedure is similar to the above, except that you must have enabled the 
delete=all feature when you compiled the module and must export the following
variable:

export DELETE_ALL=1


@


1.4
log
@* flock.sh: Test for bug 360.
@
text
@d26 9
@


1.4.4.1
log
@* unlink-all.sh, rename-all.sh, rmdir-all.sh: added check for
DELETE_ALL env variable being set to perform checks.
@
text
@a25 9
delete=all Tests
---------
The procedure is similar to the above, except that you must have enabled the 
delete=all feature when you compiled the module and must export the following
variable:

export DELETE_ALL=1


@


1.3
log
@* all files : now the files can be used for testing
unionfs over NFS as well
@
text
@d23 2
a24 2
export NFS=1;
export NFS_DIR=/dhcp/nfs; #this NFS directory where unionfs is mounted 
@


1.2
log
@* scaffold: Add symlink support.
* unlink-whiteout.sh: Add symlink tests (currently broken).
@
text
@d1 2
d17 9
@


1.1
log
@minor tweaks.
@
text
@d13 1
a13 1
contain a file type (e.g., "f" for files or "d" for directoreies), and then a
@

