I've restored the data and all kernels from Ubuntu-3.13.0-91.138 through
to the latest upstream v4.7-rc6 can attempt to mount the restored data
without oopsing the kernel. However, the data I have is definitely
broken and cannot be mounted, even btrfs-image -r on the image reports
a transid failure that is not fixable:
$ btrfs-image -r btrfs_image btrfs_image_restored
parent transid verify failed on 471304036352 wanted 407771 found 407769
parent transid verify failed on 471304036352 wanted 407771 found 407769
Ignoring transid failure
So, since the kernel is not oopsing now, I think this a fix released for
3.13
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1441150
Title:
Problems with transid in btrfs (linux 3.13)
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Fix Released
Bug description:
Hello.
We've got issues with volume mount on 3.13.0-43-generic with btrfs
after crash due to OOM. I filed bug to bugzilla on kernel.org and they
replied that bug has been fixed in newer version and it should be
backported to 3.13.
Bugzilla's original bugreport:
https://bugzilla.kernel.org/show_bug.cgi?id=96251
Trace in the kernel:
parent transid verify failed on 471304036352 wanted 407770 found 407769
parent transid verify failed on 471304036352 wanted 407770 found 407769
btrfs: failed to read log tree
btrfs: open_ctree failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1441150/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
