From: Raviu <raviu@protonmail.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Cannot mount or recover btrfs
Date: Sun, 29 Dec 2019 15:05:14 +0000 [thread overview]
Message-ID: <qxM9wPidCbIA9yMGE4e57cGzc5GkQnFF39Q2h1PLV0XTLpSVZ1nvi9wDfOD3YXIAl3GYyq2wRoG8ncoE692e0MVUah_rmDSRggyZz_trQH0=@protonmail.com> (raw)
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
[ 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
next reply other threads:[~2019-12-29 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 15:05 Raviu [this message]
2019-12-29 15:38 ` Cannot mount or recover btrfs Hugo Mills
2019-12-30 5:38 ` Qu Wenruo
2020-01-07 7:35 ` Raviu
2020-01-10 15:49 ` Raviu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='qxM9wPidCbIA9yMGE4e57cGzc5GkQnFF39Q2h1PLV0XTLpSVZ1nvi9wDfOD3YXIAl3GYyq2wRoG8ncoE692e0MVUah_rmDSRggyZz_trQH0=@protonmail.com' \
--to=raviu@protonmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.