kernel-packages team mailing list archive

[George Shuklin <1441150@xxxxxxxxxxxxxxxxxx>]

It is not a filesystem (em... original filesystem was 2Tb in size), it's
a result of btrfs-image command. I used it according to
https://btrfs.wiki.kernel.org/index.php/Btrfs-zero-log: "Please Email
the btrfs list, explain the problem, and offer your filesystem image to
a developer. "

I think there should be some way to recreate a filesystem from this meta
without actual data (inside files). But I'm not the kernel or filesystem
developer to play with this.

-- 
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 package in Ubuntu:
  In Progress

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/ubuntu/+source/linux/+bug/1441150/+subscriptions