From: "Lukáš Czerner" <lczerner@redhat.com>
To: Sankar P <sankar.curiosity@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Running xfstests on logical volumes
Date: Thu, 15 May 2014 12:56:11 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1405151244190.2112@localhost.localdomain> (raw)
In-Reply-To: <CAMSEaH6QLnWd7-VLWg67_3yzoMb0ENrjVNM9h7H8aCKBQB+=3g@mail.gmail.com>
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
next prev parent reply other threads:[~2014-05-15 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 10:05 Running xfstests on logical volumes Sankar P
2014-05-15 10:56 ` Lukáš Czerner [this message]
2014-05-15 12:53 ` Theodore Ts'o
2014-05-15 11:27 ` Azat Khuzhin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.00.1405151244190.2112@localhost.localdomain \
--to=lczerner@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sankar.curiosity@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox