linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:28:46 +0000 (UTC)	[thread overview]
Message-ID: <mi9rfe$ri6$2@ger.gmane.org> (raw)
In-Reply-To: CAJCQCtRy+RppYv5AnVb1BACWmud_yTN8qsRY2MHBKZv2K37Ykw@mail.gmail.com

On Tue, 05 May 2015 00:52:16 -0600, Chris Murphy wrote:

> On Mon, May 4, 2015 at 3:36 PM, TheJay <obiwantje@gmail.com> wrote:
> 
>> [Mon May  4 14:33:17 2015] BTRFS: bdev (null) errs: wr 3, rd 28773, flush 2, corrupt 0, gen 0
> 
> So there might be more than one thing going wrong and they're
> colliding to make a worse problem. You've got three write and 2 flush
> errors, and many thousands of read errors (probably due to missing
> devices).
> 
> It might be worth trying -o degraded,recovery because recovery can't
> work with devices missing, and degraded alone won't run the recovery
> code.
> 
> 
> -- 
> Chris Murphy

$ mount  -o degraded,recovery /dev/sdz /mnt/roms03
mount: wrong fs type, bad option, bad superblock on /dev/sdy,
       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
[Tue May  5 00:26:01 2015] BTRFS info (device sdaa): enabling auto recovery
[Tue May  5 00:26:01 2015] BTRFS info (device sdaa): disk space caching is enabled
[Tue May  5 00:26:01 2015] BTRFS: has skinny extents
[Tue May  5 00:26:01 2015] BTRFS: bdev (null) errs: wr 3, rd 28773, flush 2, corrupt 0, gen 0
[Tue May  5 00:26:05 2015] BTRFS (device sdaa): bad tree block start 8714499618262386624 1585233920
[Tue May  5 00:26:05 2015] BTRFS (device sdaa): bad tree block start 8714499618262386624 1585233920
[Tue May  5 00:26:05 2015] BTRFS (device sdaa): bad tree block start 8714499618262386624 1585233920
[Tue May  5 00:26:05 2015] BTRFS (device sdaa): bad tree block start 8714499618262386624 1585233920
[Tue May  5 00:26:05 2015] BTRFS: Failed to read block groups: -5
[Tue May  5 00:26:06 2015] BTRFS: open_ctree failed


  reply	other threads:[~2015-05-05  7:28 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 [this message]
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='mi9rfe$ri6$2@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).