linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: nick <yocto6@gmail.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: XFS Tests for Btrfs
Date: Mon, 22 Sep 2014 06:07:01 -0400	[thread overview]
Message-ID: <541FF4C5.3030005@gmail.com> (raw)
In-Reply-To: <541FDB2A.6060706@cn.fujitsu.com>



On 14-09-22 04:17 AM, Qu Wenruo wrote:
> 
> -------- Original Message --------
> Subject: Re: XFS Tests for Btrfs
> From: nick <yocto6@gmail.com>
> To: Qu Wenruo <quwenruo@cn.fujitsu.com>
> Date: 2014年09月19日 18:49
>>
>> On 14-09-18 10:46 PM, Qu Wenruo wrote:
>>> -------- Original Message --------
>>> Subject: Re: XFS Tests for Btrfs
>>> From: nick <yocto6@gmail.com>
>>> To: Qu Wenruo <quwenruo@cn.fujitsu.com>
>>> Date: 2014年09月19日 10:40
>>>> [snip]
>>>>>> Sorry Qu,ur local _scratch_mkfs routine ...
>>>>>> Error: unable to open /dev/sdc: Device or resource busy
>>>>>> check: failed to mkfs $SCRATCH_DEV using specified options
>>>>>> Passed all 0 tests
>>>>>> Is happening to me now. How do I fix this ?
>>>>>> Nick
>>>>>>
>>>>> Full local.conf please.
>>>>>
>>>>> Also lsblk output is needed.
>>>>>
>>>>> Thanks,
>>>>> Qu
>>>> Thank for the Help Qu,
>>>> Here is the output of lsblk:
>>>> NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
>>>> sda      8:0    0 111.8G  0 disk
>>>> └─sda1   8:1    0 111.8G  0 part /
>>>> sdb      8:16   0 465.8G  0 disk
>>>> ├─sdb1   8:17   0   7.6G  0 part [SWAP]
>>>> └─sdb2   8:18   0 458.1G  0 part /home
>>>> sdc      8:32   0 931.5G  0 disk
>>>> └─sdc1   8:33   0 931.5G  0 part
>>>> sr0     11:0    1  1024M  0 rom
>>>> # Ideally define at least these 4 to match your environment
>>>> # The first 2 are required.
>>>> # See README for other variables which can be set.
>>>> #
>>>> # Note: SCRATCH_DEV >will< get overwritten!
>>>>
>>>> export TEST_DEV=/dev/sdX1
>>>> export TEST_DIR=/mnt/test
>>>> export SCRATCH_DEV=/dev/sdX2
>>>> export SCRATCH_MNT=/mnt/scratch.
>>>> I am new to this so sorry for the troubles.
>>>> Nick
>>> Part your /dev/sdc into the following layout:
>>> sdc
>>>      sdc5        40G    <- Use as TEST_DEV
>>>      sdc6        15G
>>>      sdc7        15G
>>>      sdc8        15G
>>>      sdc9        15G
>>>
>>> then
>>> # mkfs.btrfs -f /dev/sdc5
>>> # mkfs.btrfs -f /dev/sdc[6-9]
>>> # mkdir -p /mnt/test
>>> # mkdir -p /mnt/scratch
>>>
>>>
>>> then write your local.conf like the following:
>>> export FSTYP=btrfs
>>> export TEST_DEV=/dev/sdc5
>>> export TEST_MNT=/mnt/test
>>> export SCRATCH_DEV_POOL="/dev/sdc6 /dev/sdc7 /dev/sdc8 /dev/sdc9"
>>> export SCRATCH_MNT=/mnt/scratch
>>>
>>> Then, you should be able to run ./check -g auto.
>>>
>>> Thanks,
>>> Qu
>> I got three failing tests now, would you like me to post the logs.
>> Nick
> There are some tests that are already known to fail but not bugs or already fixed.
> 
> As far as I can tell, if using 3.17-rc1,
> btrfs/010, btrfs/047, btrfs/054 are always failure under all mount options.
> btrfs/010 is somewhat outdated, since kernel now disables defrage with subvolume, so it will never pass.
> btrfs/047 and btrfs/054, as you can see in the comments of these tests, it's already fixed.
> Maybe next release or later RCs.
> 
> Generic/015 and generic/027 will sometims fail using nodatasum/nodatacow/compress=lzo mount options
> Also generic/275 will sometimes fail with compress=lzo, none of them is bug.
> Some btrfs features or designs make them not pass.
> 
> Geneirc/018 will always fails with nodatacow mount option, but the patch is already sent.
> 
> So if you encounters other bugs, I'll be happen to see the failed test number and test log.
> 
> BTW, as I mentioned, different mount options may cause different test results,
> so it's high recommended to run xfstest against all supported mount options.
> 
> Thanks,
> Qu
> 
> 
Qu,
I will run the tests later and see if any of them are failing beside the ones you mentioned.
Nick

      parent reply	other threads:[~2014-09-22 10:07 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
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 [this message]

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=541FF4C5.3030005@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).