[Bug 651875] New: Assertion error message with btrfsck after zypper update
https://bugzilla.novell.com/show_bug.cgi?id=651875 https://bugzilla.novell.com/show_bug.cgi?id=651875#c0 Summary: Assertion error message with btrfsck after zypper update Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: cptracey1980@warpmail.net QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-0.7.1 Firefox/3.6.12 I have two disks formatted as btrfs RAID0. The btrfs raid has one subvolume; the raid and the subvolume were mounted via /etc/fstab. The RAID worked extremely well until I did a zypper update perhaps two weeks ago. Immediately following the update, I needed to reboot the workstation. I shutdown kdm using init 3 from the system console and rebooted the machine with shutdown -r now from the system console. The workstation hung during the reboot and I had to hard power it off in order to continue with the reboot. After the power on, the btrfs raid appeard as normal, but the kernel occasionally threw oops. I did not realize at the time that the opps were related to the btrfs raid. After several days of workstation usage, the btrfs raid became inaccessible. I tried to ummount and remount it; at the mount command there was a kernel panic. I removed the mount -t btrfs command from /etc/fstab and the workstation boots and operates normally. I would like to attempt to recover the btrfs raid. Here are my actions to do so: 1. Issue command "btrfs-show" Label: HD103SJ_btrfs uuid: 2ff6e89d-b790-425b-837b-475d1504be69 Total devices 2 FS bytes used 733.80GB devid 1 size 931.51GB used 369.53GB path /dev/sdd devid 2 size 931.51GB used 369.51GB path /dev/sde Btrfs Btrfs v0.19 2. Issue command "btrfsck /dev/sde" btrfsck: disk-io.c:416: find_and_setup_root: Assertion `!(!root->node)' failed. I am trying to determine the check that the Assertion wants to make. That is, I would like to know what the btrfs module is trying to do that is causing it to fail. After spending time and posting the question to the linux-btrfs mailing list, I have concluded that the assertion is from Novell's code. Reproducible: Always Steps to Reproduce: 1.btrfsck 2. 3. Actual Results: btrfsck: disk-io.c:416: find_and_setup_root: Assertion `!(!root->node)' failed. Expected Results: ound 786721177600 bytes used err is 0 total csum bytes: 764459476 total tree bytes: 3914674176 total fs tree bytes: 2748862464 btree space waste bytes: 988776873 file data blocks allocated: 782806503424 referenced 782805028864 Btrfs Btrfs v0.19 uname -a Linux xxxxxxxx 2.6.36-fs_21-Oct #1 SMP Thu Oct 21 01:49:33 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=651875 https://bugzilla.novell.com/show_bug.cgi?id=651875#c1 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jeffm@novell.com InfoProvider| |cptracey1980@warpmail.net --- Comment #1 from Jeff Mahoney <jeffm@novell.com> 2010-11-22 20:07:00 UTC --- Can you link to the discussion? I'm afraid your conclusion is wrong and that assertion is part of the btrfsprogs 0.19 code. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=651875 https://bugzilla.novell.com/show_bug.cgi?id=651875#c2 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED CC| |jslaby@novell.com InfoProvider|cptracey1980@warpmail.net | Resolution| |NORESPONSE --- Comment #2 from Jiri Slaby <jslaby@novell.com> 2011-03-02 21:20:38 UTC --- Closed due to lack of response. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com