On Sun, Dec 29, 2019 at 03:05:14PM +0000, Raviu wrote: > Hi, > My system suddenly crashed, after reboot I cannot mount /home any more. > > `uname -a` > Linux moonIk80 4.12.14-lp151.28.36-default #1 SMP Fri Dec 6 13:50:27 UTC 2019 (8f4a495) x86_64 x86_64 x86_64 GNU/Linux > > btrfs-progs v5.4 > > `btrfs fi show` > Label: none uuid: 378faa6e-8af0-415e-93f7-68b31fb08a29 > Total devices 1 FS bytes used 194.99GiB > devid 1 size 232.79GiB used 231.79GiB path /dev/mapper/cr_sda4 > > > The device cannot be mounted. > [ 188.649876] BTRFS info (device dm-1): disk space caching is enabled > [ 188.649878] BTRFS info (device dm-1): has skinny extents > [ 188.656364] BTRFS critical (device dm-1): corrupt leaf: root=2 block=294640566272 slot=104, unexpected item end, have 42739 expect 9971 >>> hex(9971) '0x26f3' >>> hex(42739) '0xa6f3' That looks like a single bit error, and it's got a correct checksum for the incorrect data, which suggests that the error happened while the metadata was in RAM. The most likely cause here is that your RAM is bad. (There are other options, but they're also mostly hardware). As for fixing it -- first, make really, really sure that your hardware is OK. After that, I don't think btrfs check will fix it (although it might). Maybe one of the devs can add something to it to help. Hugo. > [ 188.656374] BTRFS error (device dm-1): failed to read block groups: -5 > [ 188.700088] BTRFS error (device dm-1): open_ctree failed > > > > `btrfs check /dev/mapper/cr_sda4` > Opening filesystem to check... > incorrect offsets 9971 42739 > incorrect offsets 9971 42739 > incorrect offsets 9971 42739 > ERROR: failed to read block groups: Operation not permitted > ERROR: cannot open file system > > -- Hugo Mills | I'm on a 30-day diet. So far I've lost 18 days. hugo@... carfax.org.uk | http://carfax.org.uk/ | PGP: E2AB1DE4 |
