From: Vladi Gergov <vladi@aresgate.net>
To: Chris Mason <chris.mason@facebook.com>
Cc: linux-btrfs@vger.kernel.org
Subject: btrfs raid1 degraded does not mount or fsck
Date: Sat, 9 Apr 2016 15:44:41 -0700 [thread overview]
Message-ID: <20160409224440.GC6768@gypsyops.denof.sin> (raw)
Anyone know if there is currently with updated kernel and tools a way to
recover the data on this? I have tried btrfs chunk-recovery with not
luck. Anything else I can do to try and get the data off at least?
Thanks in advance!
On Tuesday, 16.11.10 at 16:50, Chris Mason wrote:
> Excerpts from Vladi Gergov's message of 2010-10-29 16:53:42 -0400:
> > >>> gypsyops @ /mnt > sudo mount -o degraded /dev/sdc das3/
> > Password:
> > mount: wrong fs type, bad option, bad superblock on /dev/sdc,
> > missing codepage or helper program, or other error
> > In some cases useful info is found in syslog - try
> > dmesg | tail or so
> >
> > [ 684.577540] device label das4 devid 2 transid 107954 /dev/sdc
> > [ 684.595150] btrfs: allowing degraded mounts
> > [ 684.595594] btrfs: failed to read chunk root on sdb
> > [ 684.604110] btrfs: open_ctree failed
> >
> > >>> gypsyops @ /mnt > sudo btrfsck /dev/sdc
> > btrfsck: volumes.c:1367: btrfs_read_sys_array: Assertion `!(ret)' failed.
>
> Ok, I dug through this and found the bug responsible for your
> unmountable FS. When we're mounted in degraded mode, and we don't have
> enough drives available to do raid1,10, we're can use the wrong raid
> level for new allocations.
>
> I'm fixing the kernel side so this doesn't happen anymore, but I'll need
> to rebuild the chunk tree (and probably a few others) off your good disk to
> fix things.
>
> I've got it reproduced here though, so I'll make an fsck that can scan
> for the correct trees and fix it for you.
>
> Since you're basically going to be my first external fsck customer, is
> there anyway you can do a raw device based backup of the blocks? This
> way if I do mess things up we can repeat the experiment.
>
> -chris
>
> !DSPAM:4ce2fd55191821234852255!
>
>
--
,-| Vladi
`-| Gergov
next reply other threads:[~2016-04-09 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-09 22:44 Vladi Gergov [this message]
2016-04-10 6:55 ` btrfs raid1 degraded does not mount or fsck Duncan
-- strict thread matches above, loose matches on Subject: below --
2010-10-29 20:53 Vladi Gergov
2010-10-30 6:55 ` Goffredo Baroncelli
2010-11-16 21:50 ` Chris Mason
2011-10-10 4:42 ` Larry Reaves
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=20160409224440.GC6768@gypsyops.denof.sin \
--to=vladi@aresgate.net \
--cc=chris.mason@facebook.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).