From: Anand Jain <Anand.Jain@oracle.com>
To: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: bug adding device to seed device, btrfs fi show fails
Date: Mon, 12 May 2014 10:00:34 +0800 [thread overview]
Message-ID: <53702B42.8040806@oracle.com> (raw)
In-Reply-To: <29B81ECC-8877-4BBB-9701-1CB5C46717ED@colorremedies.com>
This patch posted a long time back should fix it.
http://permalink.gmane.org/gmane.comp.file-systems.btrfs/33276
Could you test it ?
Thanks, Anand
On 05/11/2014 09:51 AM, Chris Murphy wrote:
> kernel 3.15.0-0.rc5.git0.1.fc21.x86_64
> btrfs-progs 3.14
>
> /dev/sdb2 = existing btrfs fs
> /dev/sdc3 = unformatted partition
>
>
> # btrfstune -S1 /dev/sdb2
> # mount /dev/sdb2 /mnt
> mount: /dev/sdb2 is write-protected, mounting read-only
> # btrfs device add /dev/sdc3 /mnt
> Performing full device TRIM (75.90GiB) ...
> # btrfs fi show
> Label: 'rawhide' uuid: d372e5d1-386f-460c-b036-611469e0155e
> Total devices 1 FS bytes used 7.55GiB
> devid 1 size 79.31GiB used 11.04GiB path /dev/sda3
>
> btrfs: utils.c:1769: get_fs_info: Assertion `!(ndevs >= fi_args->num_devices)' failed.
>
> Nothing listed in dmesg.--
> 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-05-12 1:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 1:51 bug adding device to seed device, btrfs fi show fails Chris Murphy
2014-05-11 3:38 ` Chris Murphy
2014-05-12 2:00 ` Anand Jain [this message]
2014-05-13 9:12 ` Wang Shilong
2014-08-14 4:05 ` Chris Murphy
2014-08-14 4:37 ` Anand Jain
2014-08-14 4:42 ` Chris Murphy
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=53702B42.8040806@oracle.com \
--to=anand.jain@oracle.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 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).