btrfsck assert failure: btrfsck: disk-io.c:416: find_and_setup_root: Assertion `!(!root->node)' failed.

Bug #793410 reported by Chui
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
btrfs-tools (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: btrfs-tools

not sure if it's a hdd problem or not, but the FS is a goner :-(

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: btrfs-tools 0.19+20100601-3ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
AssertionMessage: btrfsck: disk-io.c:416: find_and_setup_root: Assertion `!(!root->node)' failed.
Date: Mon Jun 6 08:40:05 2011
ExecutablePath: /sbin/btrfsck
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: btrfsck /dev/sda3
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
Signal: 6
SourcePackage: btrfs-tools
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? ()
Title: btrfsck assert failure: btrfsck: disk-io.c:416: find_and_setup_root: Assertion `!(!root->node)' failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Chui (jan-delandtsheer) wrote :

[ 361.008941] device fsid 9a4c1ce789b4fc38-d0b3cb60e1948a93 devid 1 transid 361222 /dev/sda3
[ 361.011153] parent transid verify failed on 175882637312 wanted 361222 found 361211
[ 361.011316] parent transid verify failed on 175882637312 wanted 361222 found 361211
[ 361.011477] parent transid verify failed on 175882637312 wanted 361222 found 361211
[ 361.011481] parent transid verify failed on 175882637312 wanted 361222 found 361211
[ 361.100940] btrfs: open_ctree failed

tried to mount from usb livecd, still to no avail

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #703671, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
Revision history for this message
RussianNeuroMancer (russianneuromancer) wrote :

There is success story about recovery data in this case: http://<email address hidden>/msg11534.html (read whole thread).

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in btrfs-tools (Ubuntu):
status: New → Confirmed
Revision history for this message
DeeKey (privateinf) wrote :

Got the same problem! No power failure. Just a normal reboot. And now I am unable to mount my homefolder anymore :(

When issuing the command:
# mount -t btrfs /dev/sda5 /home

Get the following in dmesg:
[ 534.320436] device fsid dddfdf4a-a846-4a61-a749-616389fd35bc devid 1 transid 197638 /dev/sda5
[ 534.326524] parent transid verify failed on 32522240 wanted 197242 found 197636
[ 534.326535] parent transid verify failed on 32522240 wanted 197242 found 197636
[ 534.326541] parent transid verify failed on 32522240 wanted 197242 found 197636
[ 534.326546] parent transid verify failed on 32522240 wanted 197242 found 197636
[ 534.327081] btrfs: open_ctree failed

When executing
# btrfsck /dev/sda5
got the following in terminal:

parent transid verify failed on 32522240 wanted 197242 found 197636
parent transid verify failed on 32522240 wanted 197242 found 197636
parent transid verify failed on 32522240 wanted 197242 found 197636
btrfsck: disk-io.c:412: find_and_setup_root: Assertion `!(!root->node)' failed.
Aborted

This is on ubuntu 11.10 on latest default kernel. Also upgraded from PPA to Linux kernel 3.2 with no luck :(
My harddisk is SSD.

Revision history for this message
Carey Underwood (cwillu) wrote :

Btrfsck is not a repair tool; 2.6.38 has known corruption issues, and btrfs itself is still considered experimental in 3.3rc3, let alone 2.6.38.

That said, the data is almost certainly fine, so long as you don't go poking at random utilities without instruction from somebody who knows what they're doing (which means the btrfs mailing list).

Easiest first thing to try is installing a 3.2 or 3.3 kernel and attempt to mount the filesystem readonly.

Revision history for this message
Carey Underwood (cwillu) wrote :

Thou shalt keep backups when using experimental filesystems.

Revision history for this message
DeeKey (privateinf) wrote :

Tryed latest kernel versions installed from PPA on Ubuntu 11.10 x64
Linux 3.2 and Linux 3.3.0-030300rc3-generic

Unable to mount readonly and read-write.

There should be recovery utilities soon according to this presentation (see youtube 33:00)
http://www.phoronix.com/scan.php?page=news_item&px=MTA0ODU

On 3.3rc3 this does not work for me
mount -o recovery /dev/failed /mountpoint

Revision history for this message
Hercules (sithiraklis) wrote :

I faced the same bug today in Ubuntu 12.04 LTS!
I could not mount the filesystems (/boot and /home) and Ubuntu warned for fatal errors when booting.
However, if I pressed I (Ignore) I could enter successfully in my log screen.
Is this safe to ignore for the time being?

P.S.1: This happened out of the blue today from the time that Ubuntu were released still today.
P.S.2: I saw the URLs but people had problems even when mounting!

Revision history for this message
Hercules (sithiraklis) wrote :

P.S3: Log files welcome if you deem so :)

Revision history for this message
Hercules (sithiraklis) wrote :
Download full text (5.5 KiB)

More info:
Doing btrfsck in /boot gives this:
couldn't open because of unsupported option features (8).
btrfsck: disk-io.c:679: open_ctree_fd: Assertion `!(1)' failed.
Doing the same in / at first didnt found a block <number> and crashed.
Recurrent checks produce bad block checks such as (indicative output below):
Extent back ref already exists for 190476288 parent 0 root 2
Extent back ref already exists for 45932544 parent 0 root 2
Extent back ref already exists for 67600384 parent 0 root 2
Extent back ref already exists for 45928448 parent 0 root 2
Extent back ref already exists for 48345088 parent 0 root 2
Extent back ref already exists for 45899776 parent 0 root 2
Extent back ref already exists for 45879296 parent 0 root 2
Extent back ref already exists for 45862912 parent 0 root 2
Extent back ref already exists for 49606656 parent 0 root 2
Extent back ref already exists for 183283712 parent 0 root 2
Extent back ref already exists for 50061312 parent 0 root 2
Extent back ref already exists for 38305792 parent 0 root 2
Extent back ref already exists for 81879040 parent 0 root 2
Extent back ref already exists for 47153152 parent 0 root 2
Extent back ref already exists for 45846528 parent 0 root 2
Extent back ref already exists for 83390464 parent 0 root 2
Extent back ref already exists for 38326272 parent 0 root 2
Extent back ref already exists for 71688192 parent 0 root 2
parent transid verify failed on 38899712 wanted 29962 found 28637
parent transid verify failed on 38899712 wanted 29962 found 28637
parent transid verify failed on 47984640 wanted 29957 found 29884
parent transid verify failed on 47984640 wanted 29957 found 29884
parent transid verify failed on 40017920 wanted 29962 found 29944
parent transid verify failed on 40017920 wanted 29962 found 29944
bad block 47243264
parent transid verify failed on 37011456 wanted 29958 found 29944
parent transid verify failed on 37011456 wanted 29958 found 29944
leaf parent key incorrect 47464448
bad block 47464448
bad block 47685632
Extent back ref already exists for 49393664 parent 0 root 2
Extent back ref already exists for 265678848 parent 0 root 2
Extent back ref already exists for 49397760 parent 0 root 2
Extent back ref already exists for 265953280 parent 0 root 2
Extent back ref already exists for 73359360 parent 0 root 2
Extent back ref already exists for 67162112 parent 0 root 2
Extent back ref already exists for 36175872 parent 0 root 2
Extent back ref already exists for 36179968 parent 0 root 2
Extent back ref already exists for 49405952 parent 0 root 2
Extent back ref already exists for 73396224 parent 0 root 2
Extent back ref already exists for 47730688 parent 0 root 2
Extent back ref already exists for 267403264 parent 0 root 2
Extent back ref already exists for 47738880 parent 0 root 2
Extent back ref already exists for 78487552 parent 0 root 2
Extent back ref already exists for 35606528 parent 0 root 2
Extent back ref already exists for 78495744 parent 0 root 2
Extent back ref already exists for 52768768 parent 0 root 2
Extent back ref already exists for 47734784 parent 0 root 2
Extent back ref already exists for 50556928 parent 0 root 2
Ex...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.