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: Tue, 5 May 2015 07:30:18 +0000 (UTC) [thread overview]
Message-ID: <mi9ria$ri6$3@ger.gmane.org> (raw)
In-Reply-To: CAJCQCtR2hZu7Dxr1PpHyTyaDYhRMeC7Rf=we59WzRCGncZ7=QA@mail.gmail.com
On Tue, 05 May 2015 00:48:35 -0600, Chris Murphy wrote:
> On Mon, May 4, 2015 at 9:44 AM, TheJay <obiwantje@gmail.com> wrote:
>> $ sudo btrfs fi show
>> Label: 'roms03' uuid: b0025417-4045-4c63-a432-0625b7cc41ea
>> Total devices 4 FS bytes used 2.67TiB
>> devid 1 size 1.36TiB used 1.36TiB path /dev/sdz
>> devid 3 size 1.36TiB used 1.36TiB path /dev/sdaa
>> devid 4 size 1.36TiB used 1.36TiB path /dev/sdab
>> *** Some devices missing
>
> How many devices are missing?
>
>> [Mon May 4 08:35:08 2015] BTRFS: failed to read chunk tree on sdz
>
> That's not good. What do you get for 'btrfs check" (without --repair)?
>
> --
> Chris Murphy
Appriciate the response Chris
> How many devices are missing?
One (1) of the 4 devices is missing - "device 2".
> What do you get for 'btrfs check" (without --repair)?
$ btrfs check /dev/sdaa
warning, device 2 is missing
warning devid 2 not found already
checksum verify failed on 21200896 found 44715E95 wanted A092E323
checksum verify failed on 21200896 found 91AC994F wanted 987F5E0F
checksum verify failed on 21200896 found 44715E95 wanted A092E323
bytenr mismatch, want=21200896, have=65536
Couldn't read chunk tree
Couldn't open file system
next prev parent reply other threads:[~2015-05-05 7:35 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
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 [this message]
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='mi9ria$ri6$3@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 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).