Bug 728751 - btrfs partition stopped mounting... unable to recover data
Summary: btrfs partition stopped mounting... unable to recover data
Alias: None
Product: Fedora
Classification: Fedora
Component: btrfs-progs
Version: 15
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Josef Bacik
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2011-08-07 06:01 UTC by markm
Modified: 2012-08-07 16:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-08-07 16:38:20 UTC
Type: ---

Attachments (Terms of Use)
dmesg info about kernel error (3.95 KB, text/plain)
2011-08-07 06:01 UTC, markm
no flags Details

Description markm 2011-08-07 06:01:21 UTC
Created attachment 517031 [details]
dmesg info about kernel error

Description of problem:

I woke up, opened a lid of my laptop and to my surprise nothing has happened - blank screen, only dead cursor in the top right corner. Forced reboot and my btrfs /home partition no longer boots.

Version-Release number of selected component (if applicable):

$ rpm -qa | grep btrfs

$ uname -a
Linux thinkpad.mareg 2.6.40-4.fc15.x86_64 #1 SMP Fri Jul 29 18:46:53 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:


Steps to Reproduce:
1. boot
2. log in as user
Actual results:

/home partition is not mounted

Expected results:

/home partition mounted

Additional info:

from the boot messages:

Remounting root filesystem in read-write mode:  	[  OK  ]
mount: according to mtab, /dev/sda2 is already mounted on /

Mounting local filesystems:  /etc/init.d/functions: line 573:   970 Segmentation fault      "$@"

see dmesg.txt attached for details.

I have three partitions:

/dev/sda1 ext4  /boot
/dev/sda2 btrfs /
/dev/sda3 btrfs /home

I've tried running btrfsck, got the following result:

# btrfsck /dev/sda3 
root 5 inode 42866 errors 400
root 5 inode 47154 errors 400
root 5 inode 47155 errors 400
root 5 inode 400512 errors 400
root 5 inode 403721 errors 400
root 5 inode 403723 errors 400
root 5 inode 403724 errors 400
found 100093267968 bytes used err is 1
total csum bytes: 97371504
total tree bytes: 370462720
total fs tree bytes: 237899776
btree space waste bytes: 87330577
file data blocks allocated: 2937231593472
 referenced 96065196032
Btrfs Btrfs v0.19

but there is no way of fixing it.

I thought btrfs was ready for general use, is there any way I could recover data and migrate to ext4?

Comment 1 markm 2011-08-07 06:34:02 UTC
found a tip on the net: http://forum.sabayon.org/viewtopic.php?t=24317#p135832

apparently, booting into .38 allows me to access data without any issues - looks like a bug in kernel .39/.40

Comment 2 Fedora End Of Life 2012-08-07 16:38:22 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:

Note You need to log in before you can comment on or make changes to this bug.