From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: btrfs check --repair is clean, but mount fails
Date: Fri, 26 Feb 2016 18:39:38 -0800 [thread overview]
Message-ID: <20160227023938.GB5286@merlins.org> (raw)
btrfs-tools 4.4-1
gargamel:~# uname -r
4.4.2-amd64-i915-volpreempt-20160214bc2
2 drive array stopped working after a crash/reboot. Check --repair finds nothing wrong with it:
gargamel:~# btrfs check --repair /dev/mapper/raid0d1
enabling repair mode
Checking filesystem on /dev/mapper/raid0d1
UUID: 01334b81-c0db-4e80-92e4-cac4da867651
checking extents
Fixed 0 roots.
checking free space cache
cache and super generation don't match, space cache will be invalidated
checking fs roots
checking csums
checking root refs
found 1201345524312 bytes used err is 0
total csum bytes: 1165124220
total tree bytes: 8258322432
total fs tree bytes: 5574197248
total extent tree bytes: 1020428288
btree space waste bytes: 1902023247
file data blocks allocated: 1193398628352
referenced 1209324777472
gargamel:~# mount /var/local/space
mount: wrong fs type, bad option, bad superblock on /dev/mapper/raid0d1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
[ 8200.511021] BTRFS info (device dm-6): disk space caching is enabled
[ 8200.533030] BTRFS: failed to read the system array on dm-6
[ 8200.582097] BTRFS: open_ctree failed
gargamel:~# btrfs check --repair /dev/mapper/raid0d2
enabling repair mode
Checking filesystem on /dev/mapper/raid0d2
UUID: 01334b81-c0db-4e80-92e4-cac4da867651
checking extents
Fixed 0 roots.
checking free space cache
cache and super generation don't match, space cache will be invalidated
checking fs roots
checking csums
checking root refs
found 1201345540696 bytes used err is 0
total csum bytes: 1165124220
total tree bytes: 8258338816
total fs tree bytes: 5574197248
total extent tree bytes: 1020444672
btree space waste bytes: 1902039421
file data blocks allocated: 1193398628352
referenced 1209324777472
gargamel:~# mount /var/local/space
mount: wrong fs type, bad option, bad superblock on /dev/mapper/raid0d1,
[13373.606737] BTRFS info (device dm-6): disk space caching is enabled
[13373.628682] BTRFS: failed to read the system array on dm-6
[13373.672607] BTRFS: open_ctree failed
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next reply other threads:[~2016-02-27 2:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 2:39 Marc MERLIN [this message]
2016-02-27 2:45 ` btrfs check --repair is clean, but mount fails Liu Bo
2016-02-27 3:03 ` Marc MERLIN
2016-02-27 18:06 ` Liu Bo
2016-02-28 1:04 ` Marc MERLIN
2016-02-27 22:58 ` Anand Jain
2016-02-28 0:56 ` Marc MERLIN
2016-02-28 1:44 ` Anand Jain
2016-02-28 3:09 ` Marc MERLIN
2016-02-28 6:49 ` Duncan
2016-02-28 13:56 ` Marc MERLIN
2016-02-28 5:17 ` Marc MERLIN
2016-02-28 6:11 ` Anand Jain
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=20160227023938.GB5286@merlins.org \
--to=marc@merlins.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).