From: Chris Mason <clm@fb.com>
To: Chris Murphy <chris@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: kernel BUG at fs/btrfs/locking.c when mounting with previously missing device
Date: Thu, 15 May 2014 16:45:48 -0400 [thread overview]
Message-ID: <5375277C.8040008@fb.com> (raw)
In-Reply-To: <237483C1-00DF-4576-8C44-56EBCF077B9B@colorremedies.com>
On 05/15/2014 04:40 PM, Chris Murphy wrote:
> Summary: Two device btrfs raid1, as data device not boot/rootfs, mounted and filled with some data. Power off and remove one device. Reboot and mount the single device available with -o degraded. Create new subvolume and fill with some data. Poweroff and reattach previously removed device. Reboot and attempt to mount volume normally and I get a segfault.
>
> Setup:
> VBox VM, Fedora Rawhide
> 2x 2TB VDIs
> kernel 3.15.0-0.rc5.git0.1.fc21.x86_64
> btrfs-progs 3.14-1
> mkfs.btrfs -d raid1 -m raid1 /dev/sd[bc]
>
> Reproduce steps:
> 1. Mount /dev/sdb /mnt
> 2. btrfs sub create /mnt/subv1
> 3. cp -a /var /mnt/prefill/
> 4. poweroff, remove /dev/sdc
> 5. Boot, mount /dev/sdb /mnt -o degraded
> 6. btrfs sub create /mnt/subv2
> 7. cp -a /boot /mnt/sub2/
> 8. poweroff, reattach /dev/sdc
> 9. Boot, mount /dev/sdb /mnt
> Segmentation fault
>
> Regression: I know I've done this recently with existing subvolumes (without making new ones while mounting degraded) and it worked OK so I'm not sure how reproducible it is.
>
Yes, this used to work. I'll reproduce, things for sending it!
-chris
next prev parent reply other threads:[~2014-05-15 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 20:40 kernel BUG at fs/btrfs/locking.c when mounting with previously missing device Chris Murphy
2014-05-15 20:45 ` Chris Mason [this message]
2014-05-15 20:52 ` 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=5375277C.8040008@fb.com \
--to=clm@fb.com \
--cc=chris@colorremedies.com \
--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 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.