On Thu, May 15, 2014 at 12:56:11PM +0200, Lukáš Czerner wrote:
> > The volume NSSVOL is a logical device and not an actual device. When I
> > run the xfstests, I get an error:
> >
> > common/config: Error: $TEST_DEV (NSSVOL) is not a block device or a
> > NFS filesystem
> >
> > How do I resolve this ? Is it possible to test such logical devices ?
>
> I do not know of any other way other than modify xfstests sources,
> specifically common/rc helpers, common/config checks and possibly
> more and update mkfs and fsck routines. xfstests simply expects
> block device or NFS, so you'll have to teach it to understand your
> file system as well.
This is hacky as all hell, but something Vaibhav came up with when
testing unionfs was to do the following:
# mkdir /root/unionfs_play_area
# cd /root/unionfs_play_area
# mkdir ro_layer rw_layer unionfs:mnt
# export TEST_DIR=/root/unionfs_play_area/unionfs:mnt
# export TEST_DEV=/root/unionfs_play_area/unionfs:mnt
# export MOUNT_OPTIONS="-o
dirs=/root/unionfs_play_area/rw_layer=rw:/root/unionfs_play_area/ro_layer=ro"
# export TEST_FS_MOUNT_OPTS="-o
dirs=/root/unionfs_play_area/rw_layer=rw:/root/unionfs_play_area/ro_layer=ro"
The trick is to use a device name that contains a ':' which makes
xfstest treat it as a NFS specification. Then the only other change
which me made was pretty trivial:
--- check.orig 2014-05-13 10:50:13.000000000 -0700
+++ check 2014-05-12 18:01:12.000000000 -0700
@@ -62,7 +62,7 @@
get_fstyp_arg()
{
if [ "$1" == "-udf" -o "$1" == "-xfs" -o "$1" == "-nfs" -o \
- "$1" == "-tmpfs" ]; then
+ "$1" == "-unionfs" -o "$1" == "-tmpfs" ]; then
echo $1 | cut -c 2-
fi
}
@@ -105,6 +105,7 @@
-udf test UDF
-nfs test NFS
-tmpfs test TMPFS
+ -unionfs test UNIONFS
-l line mode diff
-udiff show unified diff (default)
-n show me, do not run tests
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
