All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Reaves <larry@yrral.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs raid1 degraded does not mount or fsck
Date: Mon, 10 Oct 2011 04:42:04 +0000 (UTC)	[thread overview]
Message-ID: <loom.20111010T063606-854@post.gmane.org> (raw)
In-Reply-To: 1289943080-sup-1244@think

Chris Mason <chris.mason <at> oracle.com> writes:

> 
> 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

I'm seeing this same error, uname -a shows:
2.6.38-11-generic
although, my fs went down a month or so ago so it could have been a slightly
earlier Ubuntu kernel.  Is this the same issue?  Is that very targeted fsck
available somewhere?  I've got my replacement disk ready to add, I just need to
get the other 3 mounted.  Data and metadata are both raid10.  I really need to
start tracking the kernel again :(.  Thanks for any help.

-Larry


  reply	other threads:[~2011-10-10  4:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29 20:53 btrfs raid1 degraded does not mount or fsck Vladi Gergov
2010-10-30  6:55 ` Goffredo Baroncelli
2010-11-16 21:50 ` Chris Mason
2011-10-10  4:42   ` Larry Reaves [this message]
2012-09-17 20:38 ` btrfs raid1 degraded in need of chuck tree rebuild Vladi Gergov
  -- strict thread matches above, loose matches on Subject: below --
2016-04-09 22:44 btrfs raid1 degraded does not mount or fsck Vladi Gergov
2016-04-10  6:55 ` Duncan

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=loom.20111010T063606-854@post.gmane.org \
    --to=larry@yrral.net \
    --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.