Running xfstests on logical volumes

Running xfstests on logical volumes

[Sankar P]

Hi,

I am trying to run the generic group of tests, on an out-of-tree
filesystem http://en.wikipedia.org/wiki/Novell_Storage_Services

I run as:
TEST_DEV=NSSVOL TEST_DIR=/media/nss/NSSVOL FSTYP=nssvol ./check -g dir 001

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 ?
Also, the filesystem does not have a fsck too, if it matters. I could
not get any information about this from README. I am running xfstests
current git head.

-- 
Sankar P
http://psankar.blogspot.com

Re: Running xfstests on logical volumes

[Lukáš Czerner]

On Thu, 15 May 2014, Sankar P wrote:

> Date: Thu, 15 May 2014 15:35:37 +0530
> From: Sankar P <sankar.curiosity@gmail.com>
> To: linux-fsdevel@vger.kernel.org
> Subject: Running xfstests on logical volumes
> 
> Hi,
> 
> I am trying to run the generic group of tests, on an out-of-tree
> filesystem http://en.wikipedia.org/wiki/Novell_Storage_Services
> 
> I run as:
> TEST_DEV=NSSVOL TEST_DIR=/media/nss/NSSVOL FSTYP=nssvol ./check -g dir 001
> 
> 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.

> Also, the filesystem does not have a fsck too, if it matters. I could
> not get any information about this from README. I am running xfstests
> current git head.

-Lukas

Re: Running xfstests on logical volumes

[Azat Khuzhin]

On Thu, May 15, 2014 at 03:35:37PM +0530, Sankar P wrote:
> Hi,
> 
> I am trying to run the generic group of tests, on an out-of-tree
> filesystem http://en.wikipedia.org/wiki/Novell_Storage_Services
> 
> I run as:
> TEST_DEV=NSSVOL TEST_DIR=/media/nss/NSSVOL FSTYP=nssvol ./check -g dir 001
> 
> 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 ?
> Also, the filesystem does not have a fsck too, if it matters. I could
> not get any information about this from README. I am running xfstests
> current git head.

Hi Sankar,

As for mkfs, you could just symlinking /bin/true, somethink like this:
$ ln -s /bin/true /sbin/fsck.$FSTYP

> 
> -- 
> Sankar P
> http://psankar.blogspot.com
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Respectfully
Azat Khuzhin

Re: Running xfstests on logical volumes

[Theodore Ts'o]

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html