From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-progs 4.0 breaks btrfs fi show?
Date: Wed, 6 May 2015 16:12:08 +0800 [thread overview]
Message-ID: <5549CCD8.2010000@cn.fujitsu.com> (raw)
In-Reply-To: <CAJCQCtR7ZT6vt06fbw3sh9sQxufsck=v2J+HJKz2DLFxR9q8RQ@mail.gmail.com>
Works for me.
Although with a lot of annoying extra missing device warning:
------
$ sudo btrfs fi show
warning, device 1 is missing
warning, device 4 is missing
warning, device 3 is missing
warning, device 2 is missing
warning, device 1 is missing
warning devid 1 not found already
warning devid 2 not found already
warning devid 3 not found already
warning devid 4 not found already
bytenr mismatch, want=40222720, have=0
Couldn't read tree root
warning, device 1 is missing
warning, device 1 is missing
warning devid 1 not found already
Label: none uuid: 7d57b997-1e84-4daf-a99c-a0339d268112
Total devices 5 FS bytes used 6.98MiB
devid 5 size 10.00GiB used 1.80GiB path /dev/sda6
*** Some devices missing
Label: none uuid: 54e051a4-0a9b-4ec5-b8bf-cecdd1ec6620
Total devices 1 FS bytes used 991.94MiB
devid 1 size 10.00GiB used 3.04GiB path /dev/sdb
Label: none uuid: 2b4ca7ea-061a-4784-b2de-c7d6341ef8a0
Total devices 1 FS bytes used 384.00KiB
devid 1 size 15.00GiB used 2.04GiB path /dev/sdc
Label: none uuid: c5a72536-5319-465e-81b6-a03468daab8a
Total devices 4 FS bytes used 15.29MiB
devid 2 size 10.00GiB used 2.01GiB path /dev/sdg
devid 3 size 10.00GiB used 2.01GiB path /dev/sde
devid 4 size 10.00GiB used 2.01GiB path /dev/sdf
*** Some devices missing
btrfs-progs v4.0
------
Would you please give some detail of your problem?
Like the options and arguments.
Thanks,
Qu
-------- Original Message --------
Subject: btrfs-progs 4.0 breaks btrfs fi show?
From: Chris Murphy <lists@colorremedies.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Date: 2015年05月06日 15:23
> Since the 4.0 update, fi show only gives me a version number. Anyone else?
>
> btrfs-progs-4.0-1.fc22.x86_64
> kernel-4.0.1-300.fc22.x86_64
>
>
next prev parent reply other threads:[~2015-05-06 8:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 7:23 btrfs-progs 4.0 breaks btrfs fi show? Chris Murphy
2015-05-06 8:12 ` Qu Wenruo [this message]
2015-05-06 8:34 ` Anand Jain
2015-05-06 15:07 ` David Sterba
2015-05-06 15:27 ` David Sterba
[not found] ` <CAJCQCtT0ff8fVrMQ7rrgW1VFkiBL+f_upGOUZ7DY65N62jAsBQ@mail.gmail.com>
2015-05-06 9:31 ` Qu Wenruo
2015-05-06 15:52 ` Chris Murphy
2015-05-06 17:05 ` Chris Murphy
2015-05-06 17:32 ` Austin S Hemmelgarn
2015-05-06 17:48 ` Hugo Mills
2015-05-07 14:14 ` 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=5549CCD8.2010000@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.