Created attachment 462425 [details] Screenshot of systemd crash #1 Description of problem: When I try to boot my system with my disc which includes btrfs subvols, the systemd and then kernel crashes. The two traces are included at screenshots. Version-Release number of selected component (if applicable): systemd-13-1.fc15.x86_64 kernel-2.6.36.1-7.rc1.fc15.x86_64 How reproducible: relevant part of the /etc/fstab UUID=00053a82-4d2d-4f28-b576-ac614be9bae6 /home/media btrfs defaults,subvol=home_media 1 1 UUID=00053a82-4d2d-4f28-b576-ac614be9bae6 /usr/local/games btrfs defaults,subvol=games 1 1 Steps to Reproduce: 1. start system with above mentioned disc 2. crash of systemd and later kernel 3.
Created attachment 462426 [details] Screenshot of systemd crash #2
Created attachment 462428 [details] Screenshot of systemd crash #3
I forgot to add that the system boots correctly when init=/sbin/upstart is set or the disc is powered down. Whe system boots, there is no problem to use mount -a to mount it.
systemd merely exposes a btrfs bug here. The first trace is the same as in: https://bugzilla.redhat.com/show_bug.cgi?id=650261#c17 Ian Kent seems to be working on it and has posted a kernel to test. *** This bug has been marked as a duplicate of bug 650261 ***
According to the request from Ian, I reopened it for rawhide kernel and changed component to the kernel.
Looking at the screen shots this may be the same issue but I can't be sure. I can prepare patches for our Rawhide kernel so we can test it but Josef hasn't finalized the upstream submission yet so we will need to wait a bit longer before we consider requesting they be included in a release kernel.
Created attachment 463405 [details] Patch - fix error handling in btrfs_get_sb() It seems 2.6.36 is closer to 2.6.35 than I thought for btrfs. This patch must have gone into 2.6.37 so it is still needed in Rawhide for the moment.
Created attachment 463406 [details] Patch - setup blank root and fs_info for mount time I've tried to make this as close to what I think Josef will post upstream.
Created attachment 463407 [details] Patch - fix race between btrfs_get_sb() and umount The evidence shows we need this too.
Can you give this kernel a try please: http://people.redhat.com/~ikent/kernel-2.6.36.1-9.bz656465.1
This kernel fixes the bug for me and I haven't noticed any negative effects during brief testing.
Ian, should we merge this patch?
*** Bug 660015 has been marked as a duplicate of this bug. ***
(In reply to comment #12) > Ian, should we merge this patch? Yes, I think so. Anyone who tested this found these patches fix the problem. The changes have gone upstream, except for a corner case potential memory leak.
OK, rawhide is now on 2.6.37-rc5, so these bugs are fixed there. I'll grab the fixes for the other releases (which should be going to .36 as soon as I get a bit of time...)
Ok, got the fixes for F-14. Thanks for debugging this, Ian.
Created attachment 468182 [details] Crash pulling mounted USB drive The kernel-2.6.36.1-9.bz656465.1 no longer crashes on mount for me, but it now crashes if I remove a USB hard-drive while mounted and then attempt a manual unmount.
(In reply to comment #17) > Created attachment 468182 [details] > Crash pulling mounted USB drive > > The kernel-2.6.36.1-9.bz656465.1 no longer crashes on mount for me, but it now > crashes if I remove a USB hard-drive while mounted and then attempt a manual > unmount. We don't want to confuse matters. The trace shows fairly clearly this is a different bug so I'm not going to complicate matters by now starting to wrk on that. The problem is that if we just continue on solving one bug after another in the same report we end up not getting any fixes pushed out. Please open another bug for this.
Comment on attachment 468182 [details] Crash pulling mounted USB drive > Please open another bug for this. Done - bug 662547
I can confirm that rawhide kernel 2.6.37-0.rc5.git2.1.fc15.x86_64 fixes the bug for me. Should we close it?
(In reply to comment #20) > I can confirm that rawhide kernel 2.6.37-0.rc5.git2.1.fc15.x86_64 fixes the bug > for me. Should we close it? Yes, I think so. We probably should leave it open a little while longer for people to find when looking. Making it MODIFIED hopefully won't won't make it harder to find and indicates the change has been applied.
kernel-2.6.35.10-68.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/kernel-2.6.35.10-68.fc14
kernel-2.6.35.10-69.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/kernel-2.6.35.10-69.fc14
kernel-2.6.35.10-72.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/kernel-2.6.35.10-72.fc14
kernel-2.6.35.10-72.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update kernel'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/kernel-2.6.35.10-72.fc14
kernel-2.6.35.10-72.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.