From: TheJay <obiwantje@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [REQ] Help to gain access to btrfsraid6 pool that won't mount
Date: Mon, 4 May 2015 21:36:35 +0000 (UTC) [thread overview]
Message-ID: <mi8op3$ri6$1@ger.gmane.org> (raw)
In-Reply-To: 5547E3BF.4090901@inwind.it
On Mon, 04 May 2015 23:25:19 +0200, Goffredo Baroncelli wrote:
> A disk is missing, in this case you should use the "degraded" mount option:
>
> mount -o degraded /dev/sdaa /mnt/roms03
Goffredo - Thanks for responding - I tried that, but to no avail:
$ sudo mount -o degraded /dev/sdaa /mnt/roms03
mount: wrong fs type, bad option, bad superblock on /dev/sdaa,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
$ dmesg -T|tail
[Mon May 4 14:33:17 2015] BTRFS info (device sdaa): allowing degraded mounts
[Mon May 4 14:33:17 2015] BTRFS info (device sdaa): disk space caching is enabled
[Mon May 4 14:33:17 2015] BTRFS: has skinny extents
[Mon May 4 14:33:17 2015] BTRFS: bdev (null) errs: wr 3, rd 28773, flush 2, corrupt 0, gen 0
[Mon May 4 14:33:22 2015] BTRFS (device sdaa): bad tree block start 8714499618262386624 1585233920
[Mon May 4 14:33:22 2015] BTRFS (device sdaa): bad tree block start 8714499618262386624 1585233920
[Mon May 4 14:33:22 2015] BTRFS (device sdaa): bad tree block start 8714499618262386624 1585233920
[Mon May 4 14:33:22 2015] BTRFS (device sdaa): bad tree block start 8714499618262386624 1585233920
[Mon May 4 14:33:22 2015] BTRFS: Failed to read block groups: -5
[Mon May 4 14:33:22 2015] BTRFS: open_ctree failed
next prev parent reply other threads:[~2015-05-04 21:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 15:44 [REQ] Help to gain access to btrfsraid6 pool that won't mount TheJay
2015-05-04 21:25 ` Goffredo Baroncelli
2015-05-04 21:36 ` TheJay [this message]
2015-05-05 6:52 ` Chris Murphy
2015-05-05 7:28 ` TheJay
2015-05-05 6:48 ` Chris Murphy
2015-05-05 7:30 ` TheJay
2015-05-06 11:55 ` Duncan
2015-05-06 16:45 ` TheJay
2015-05-06 17:47 ` TheJay
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='mi8op3$ri6$1@ger.gmane.org' \
--to=obiwantje@gmail.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.