Adam No. I have BTRFS file system upon a LUKS volume. I first unlock LUKS and then I get a dm-mapped btrfs Filesystem. I used to be able to mount this filesystem but not anymore -------- This is the dmesg for ro,recovery,nospace_cache,nospace_cache
[21680.563023] BTRFS info (device dm-12): enabling auto recovery [21680.563044] BTRFS info (device dm-12): disabling disk space caching [21680.563059] BTRFS: has skinny extents [21680.583128] BTRFS: bdev /dev/mapper/ee errs: wr 18, rd 0, flush 0, corrupt 0, gen 0 [21680.588884] BTRFS (device dm-12): parent transid verify failed on 59162624 wanted 134868 found 54964 [21680.591339] BTRFS (device dm-12): parent transid verify failed on 59162624 wanted 134868 found 54964 [21680.591358] BTRFS: Failed to read block groups: -5 [21680.620285] BTRFS: open_ctree failed a subsequent btrfs rescue zero-log give this sudo btrfs rescue zero-log /dev/mapper/jj parent transid verify failed on 59162624 wanted 134868 found 54964 parent transid verify failed on 59162624 wanted 134868 found 54964 parent transid verify failed on 59162624 wanted 134868 found 54964 parent transid verify failed on 59162624 wanted 134868 found 54964 Ignoring transid failure leaf parent key incorrect 59162624 parent transid verify failed on 408584192 wanted 130813 found 53737 parent transid verify failed on 408584192 wanted 130813 found 53737 parent transid verify failed on 408584192 wanted 130813 found 53737 parent transid verify failed on 408584192 wanted 130813 found 53737 Ignoring transid failure Clearing log on /dev/mapper/jj, previous log_root 0, level 0 parent transid verify failed on 59162624 wanted 134868 found 54964 Ignoring transid failure parent transid verify failed on 59162624 wanted 134868 found 54964 Ignoring transid failure parent transid verify failed on 87556096 wanted 134922 found 54980 parent transid verify failed on 87556096 wanted 134922 found 54980 parent transid verify failed on 87556096 wanted 134922 found 54980 parent transid verify failed on 87556096 wanted 134922 found 54980 Ignoring transid failure parent transid verify failed on 59162624 wanted 134868 found 54964 Ignoring transid failure parent transid verify failed on 466993152 wanted 135739 found 53864 parent transid verify failed on 466993152 wanted 135739 found 53864 parent transid verify failed on 466993152 wanted 135739 found 53864 parent transid verify failed on 466993152 wanted 135739 found 53864 Ignoring transid failure parent transid verify failed on 59162624 wanted 134868 found 54964 Ignoring transid failure parent transid verify failed on 262455296 wanted 135295 found 53548 parent transid verify failed on 262455296 wanted 135295 found 53548 parent transid verify failed on 262455296 wanted 135295 found 53548 parent transid verify failed on 262455296 wanted 135295 found 53548 Ignoring transid failure parent transid verify failed on 59162624 wanted 134868 found 54964 Ignoring transid failure parent transid verify failed on 45613056 wanted 134843 found 54949 parent transid verify failed on 45613056 wanted 134843 found 54949 parent transid verify failed on 45613056 wanted 134843 found 54949 parent transid verify failed on 45613056 wanted 134843 found 54949 Ignoring transid failure parent transid verify failed on 59162624 wanted 134868 found 54964 Ignoring transid failure parent transid verify failed on 522469376 wanted 135880 found 53946 parent transid verify failed on 522469376 wanted 135880 found 53946 parent transid verify failed on 522469376 wanted 135880 found 53946 parent transid verify failed on 522469376 wanted 135880 found 53946 Ignoring transid failure No other methods seem to work Dont exactly know why this has gone to this bad state. A strings on the dm device does show my data on datablocks On Sun, Feb 14, 2016 at 7:10 PM, Adam Wilson <mox...@riseup.net> wrote: > On Sun, 14 Feb 2016 17:05:51 +0100 Bhasker C V <bhas...@unixindia.com> > wrote: > > > Hi, > > > > I have a home dir btrfs on top of luks > > Surely you mean LUKS on top of btrfs? > >
