From: "Jason D. Michaelson" <jasondmichaelson@gmail.com>
To: "'Chris Murphy'" <lists@colorremedies.com>
Cc: "'Btrfs BTRFS'" <linux-btrfs@vger.kernel.org>
Subject: RE: raid6 file system in a bad state
Date: Tue, 11 Oct 2016 10:52:14 -0500 [thread overview]
Message-ID: <5e8501d223d7$715a9bb0$540fd310$@com> (raw)
In-Reply-To: <CAJCQCtR_zOd=1hVrKAD_kKfE_EKZQ2omfWQV556Rg=OSbvEd0w@mail.gmail.com>
> -----Original Message-----
> From: chris@colorremedies.com [mailto:chris@colorremedies.com] On
> Behalf Of Chris Murphy
> Sent: Monday, October 10, 2016 11:23 PM
> To: Jason D. Michaelson
> Cc: Chris Murphy; Btrfs BTRFS
> Subject: Re: raid6 file system in a bad state
>
> What do you get for
>
> btrfs-find-root <dev>
root@castor:~/logs# btrfs-find-root /dev/sda
parent transid verify failed on 5752357961728 wanted 161562 found 159746
parent transid verify failed on 5752357961728 wanted 161562 found 159746
Couldn't setup extent tree
Superblock thinks the generation is 161562
Superblock thinks the level is 1
There's no further output, and btrfs-find-root is pegged at 100%.
At the moment, the perceived bad disc is connected. I received the same results without as well.
> btrfs rescue super-recover -v <dev>
root@castor:~/logs# btrfs rescue super-recover -v /dev/sda
All Devices:
Device: id = 2, name = /dev/sdh
Device: id = 3, name = /dev/sdd
Device: id = 5, name = /dev/sdf
Device: id = 6, name = /dev/sde
Device: id = 4, name = /dev/sdg
Device: id = 1, name = /dev/sda
Before Recovering:
[All good supers]:
device name = /dev/sdd
superblock bytenr = 65536
device name = /dev/sdd
superblock bytenr = 67108864
device name = /dev/sdd
superblock bytenr = 274877906944
device name = /dev/sdf
superblock bytenr = 65536
device name = /dev/sdf
superblock bytenr = 67108864
device name = /dev/sdf
superblock bytenr = 274877906944
device name = /dev/sde
superblock bytenr = 65536
device name = /dev/sde
superblock bytenr = 67108864
device name = /dev/sde
superblock bytenr = 274877906944
device name = /dev/sdg
superblock bytenr = 65536
device name = /dev/sdg
superblock bytenr = 67108864
device name = /dev/sdg
superblock bytenr = 274877906944
device name = /dev/sda
superblock bytenr = 65536
device name = /dev/sda
superblock bytenr = 67108864
device name = /dev/sda
superblock bytenr = 274877906944
[All bad supers]:
device name = /dev/sdh
superblock bytenr = 65536
device name = /dev/sdh
superblock bytenr = 67108864
device name = /dev/sdh
superblock bytenr = 274877906944
Make sure this is a btrfs disk otherwise the tool will destroy other fs, Are you sure? [y/N]: n
Aborted to recover bad superblocks
I aborted this waiting for instructions on whether to proceed from the list.
>
>
>
> It shouldn't matter which dev you pick, unless it face plants, then try
> another.
next prev parent reply other threads:[~2016-10-11 15:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 16:04 raid6 file system in a bad state Jason D. Michaelson
2016-10-10 20:59 ` Chris Murphy
[not found] ` <5ce201d22364$96702780$c3507680$@com>
2016-10-11 4:23 ` Chris Murphy
2016-10-11 15:52 ` Jason D. Michaelson [this message]
2016-10-11 16:06 ` Chris Murphy
2016-10-11 16:10 ` Jason D. Michaelson
2016-10-11 17:41 ` Chris Murphy
[not found] ` <5e8701d223f1$c7ea0960$57be1c20$@com>
2016-10-11 20:38 ` Chris Murphy
2016-10-12 17:59 ` Jason D. Michaelson
2016-10-12 19:36 ` Chris Murphy
2016-10-14 21:54 ` Chris Murphy
2016-10-17 18:52 ` Jason D. Michaelson
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='5e8501d223d7$715a9bb0$540fd310$@com' \
--to=jasondmichaelson@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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).