From: nick <yocto6@gmail.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: XFS Tests for Btrfs
Date: Thu, 18 Sep 2014 21:41:52 -0400 [thread overview]
Message-ID: <541B89E0.5010905@gmail.com> (raw)
In-Reply-To: <541B8993.1000604@cn.fujitsu.com>
On 14-09-18 09:40 PM, Qu Wenruo wrote:
>
> -------- Original Message --------
> Subject: Re: XFS Tests for Btrfs
> From: nick <yocto6@gmail.com>
> To: Qu Wenruo <quwenruo@cn.fujitsu.com>, <linux-btrfs@vger.kernel.org>
> Date: 2014年09月19日 09:17
>>
>> On 14-09-18 09:08 PM, Qu Wenruo wrote:
>>> Hi,
>>>
>>> Xfstests uses several environment variants to setup the test environment.
>>> You can set it manually using export, or write them into local.conf in xfstests directory.
>>>
>>> These environment variants are mandatory:
>>> TEST_DEV: device for normal tests, like all generic tests
>>> TEST_DIR: where TEST_DEV is mounted to.
>>>
>>> And somecommon optional environment variants:
>>> SCRATCH_DEV: scratch device for some tests, if you want to test btrfs' multi device related feature, you need
>>> to set SCRATCH_DEV_POOL.
>>> SCRATCH_DEV_POOL: a list for devices mainly for btrfs' muti-device related test.
>>> SCRATCH_MNT: where SCRATCH_DEV/SCRATCH_DEV_POOL is mounted to.
>>>
>>> SCRATCH_DEV_POOL should not contain the TEST_DEV.
>>>
>>> FSTYP: the filesystem type you want to test.
>>> MKFS_OPTIONS: the mkfs time options. Useful to test mkfs time feature like no-holes.
>>> MOUNT_OPTIONS: the mount time options. Useful to test feature like compress.
>>>
>>> So short guide on how to run xfstests:
>>> 1. download the xfstests source, better the git version
>>>
>>> 2. compile xfstests
>>> make will do everything for you, except you lacks some headers or dependency.
>>> When that happens, follow your distribution's method to install them.
>>>
>>> 3. setup the environment variants
>>> Manually or into the local.conf is both OK.
>>>
>>> 4. run tests
>>> You can run all tests by ./check -g auto, or multiple/single test using blob/testcase number like:
>>> # ./check generic/311
>>> # ./check btrfs/[0-9][0-9][0-9]
>>>
>>> Thanks
>>> Qu
>>>
>>> -------- Original Message --------
>>> Subject: XFS Tests for Btrfs
>>> From: nick <yocto6@gmail.com>
>>> To: <linux-btrfs@vger.kernel.org>
>>> Date: 2014年09月19日 04:14
>>>> Hey Fellow Btrfs Developers,
>>>> I am wondering how to run the xfs tests for btrfs as I tried to do it based on a link online
>>>> written I believe a few years ago. If someone can help me get set up for testing the btrfs
>>>> code using xfs tests that would be great. In addition afterwards I already build kernel 3.17
>>>> r5 release candidate and would be glad to run any times you need run to test single drive
>>>> config issues.
>>>> Thanks Nick
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> The issue I was hitting was my TEST_DIR not being configured properly. I will list my variables below.
>> /dev/sdc1 was my TEST_DEV
>> /media/nick/x was my TEST_DIR
>> Nick
> Did you mkfs on TEST_DEV? Can TEST_DEV be mounted correctly?
>
> Thanks,
> Qu
I partitioned it using gparted and I can mount it normally but not with xfstests.
Nick
next prev parent reply other threads:[~2014-09-19 1:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 20:14 XFS Tests for Btrfs nick
2014-09-19 1:08 ` Qu Wenruo
2014-09-19 1:17 ` nick
2014-09-19 1:40 ` Qu Wenruo
2014-09-19 1:41 ` nick [this message]
2014-09-19 1:46 ` Qu Wenruo
2014-09-19 1:56 ` nick
[not found] ` <541B8C90.7030503@gmail.com>
[not found] ` <541B90C8.60806@cn.fujitsu.com>
[not found] ` <541B9591.7040509@gmail.com>
[not found] ` <541B9680.5020309@cn.fujitsu.com>
[not found] ` <541B9783.2020609@gmail.com>
[not found] ` <541B98EE.1070908@cn.fujitsu.com>
[not found] ` <541C0A4D.80501@gmail.com>
[not found] ` <541FDB2A.6060706@cn.fujitsu.com>
2014-09-22 10:07 ` nick
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=541B89E0.5010905@gmail.com \
--to=yocto6@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).