From: Anand Jain <Anand.Jain@oracle.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org, clm@fb.com
Subject: Re: [PATCH 1/1] btrfs-progs: introduce a proper structure on which cli will call register-device ioctl
Date: Thu, 16 Oct 2014 23:19:43 +0800 [thread overview]
Message-ID: <543FE20F.9030501@oracle.com> (raw)
In-Reply-To: <543FDCA5.9060908@oracle.com>
I have all 6 patches,
----
e56117f btrfs-progs: optimize btrfs_scan_lblkid() for multiple calls
4d76f5f btrfs-progs: introduce btrfs_register_all_device()
7dd7ef7 btrfs-progs: code optimize cmd_scan_dev() use
btrfs_register_one_device()
7158fe7 btrfs-progs: open RW to register device using btrfs-control
6bba89f btrfs-progs: introduce a proper structure on which cli will call
register-device ioctl
df572b7 btrfs-progs: mkfs should be consistent in calling register device
----
you might have only below 3. I tried with that sub-set too but still
it does not fail here.
Thanks, Anand
On 10/16/14 22:56, Anand Jain wrote:
>
>
> On 10/16/14 18:20, David Sterba wrote:
>> On Thu, Oct 16, 2014 at 12:08:41PM +0200, David Sterba wrote:
>>> @@ -22,18 +22,21 @@
>>> <NUMDEVS> [SCRATCH_DEV].read_io_errs <NUM>
>>> <NUMDEVS> [SCRATCH_DEV].write_io_errs <NUM>
>>> == Show device stats by first/scratch dev
>>> +ERROR: ioctl(BTRFS_IOC_GET_DEV_STATS) on �oh failed: No such
>>> device
>>> [SCRATCH_DEV].corruption_errs <NUM>
>>> [SCRATCH_DEV].flush_io_errs <NUM>
>>> [SCRATCH_DEV].generation_errs <NUM>
>>
>> Additional info:
>>
>> syslog:
>>
>> [ 1332.330541] run xfstest btrfs/006
>> [ 1333.251419] BTRFS: device fsid 02ad1ce3-85e4-41c0-8d54-138a8d950b3d
>> devid 1 transid 3 /dev/sda9
>> [ 1333.273512] BTRFS: device fsid 02ad1ce3-85e4-41c0-8d54-138a8d950b3d
>> devid 2 transid 3 /dev/sda10
>> [ 1333.345285] BTRFS: device fsid 02ad1ce3-85e4-41c0-8d54-138a8d950b3d
>> devid 3 transid 3 /dev/sda11
>> [ 1333.366160] BTRFS: device fsid 02ad1ce3-85e4-41c0-8d54-138a8d950b3d
>> devid 4 transid 3 /dev/sda12
>> [ 1334.468250] BTRFS info (device sda12): disk space caching is enabled
>> [ 1334.476280] BTRFS: flagging fs with big metadata feature
>> [ 1334.491801] BTRFS: creating UUID tree
>> [ 1334.774684] BTRFS warning (device sda12): get dev_stats failed,
>> device not found
>> [ 1334.805125] BTRFS warning (device sda12): get dev_stats failed,
>> device not found
>> [ 1334.832683] BTRFS warning (device sda12): get dev_stats failed,
>> device not found
>>
>> $ btrfs fi show
>>
>> Label: 'TestLabel.006' uuid: 02ad1ce3-85e4-41c0-8d54-138a8d950b3d
>> Total devices 4 FS bytes used 192.00KiB
>> devid 1 size 10.00GiB used 20.00MiB path /dev/sda9
>> devid 2 size 10.00GiB used 256.00MiB path /dev/sda10
>> devid 3 size 10.00GiB used 0.00B path /dev/sda11
>> devid 4 size 10.00GiB used 0.00B path /dev/sda12
>>
>> SCRATCH_DEV_POOL=/dev/sda9 /dev/sda10 /dev/sda11 /dev/sda12
>
>
> Quite strange. I didn't see that problem here.
> ----
> btrfs/006 12s ... 13s
> Ran: btrfs/006
> Passed all 1 tests
> ---
>
> Can you retain the scratch mounted and check what is the output of
> 'btrfs fi show -m' (when the SCRATCH is mounted).
>
> OR /proc/fs/btrfs/devlist (in case if you have that) would help
> to debug this.
>
> OR could you restart test with a wipe all disk ?
>
> Thanks, Anand
>
>
>
> --
> 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
next prev parent reply other threads:[~2014-10-16 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 0:46 [PATCH 1/1] btrfs-progs: introduce a proper structure on which cli will call register-device ioctl Anand Jain
2014-10-16 10:08 ` David Sterba
2014-10-16 10:20 ` David Sterba
2014-10-16 14:56 ` Anand Jain
2014-10-16 15:19 ` Anand Jain [this message]
2014-10-17 15:39 ` David Sterba
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=543FE20F.9030501@oracle.com \
--to=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
/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).