archive mirror
 help / color / mirror / Atom feed
From: Chris Murphy <>
To: Btrfs BTRFS <>
Subject: Re: mount hangs after disk crash (RAID-1)
Date: Thu, 22 May 2014 12:20:41 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20140522185025.4c72aab9@s9>

On May 22, 2014, at 11:50 AM, Tomasz Chmielewski <> wrote:

>> Try -o recovery,degraded
>> I would drop the other options for now, since they aren't necessary
>> to recover from a \ device failure.
> Yes I've tried that as well, and it ends in the similar "hang" - high
> IO for a while, then no IO at all, mount does not return.
> It *does* mount as ro,degraded, but then, it's not possible to add a
> disk and recover to a functioning RAID-1.
> Also, when I try to remount rw, the mount command hangs as well.
> Is there anything else I can try?

It sounds like it's able to read the file system but in the course of repairing whatever problems it has, it's getting stuck. 

I'd mount it ro and make sure its backup is updated. Then take a btrfs image btrfs-image -c 9 -t <cores> in case a dev wants to look at the fs at some point it its current state.

Then you can try some other things if you want: btrfs-next is one direction, and also regression testing with older kernels is also reasonable.

Last you could try btrfs-zero-log, but this doesn't look like the typical case for it, and probably will make things worse so it's not the next thing to try. Also I don't expect btrfs check or even --repair to work. I've not yet had any luck with it working on degraded volumes, and even rejoined volumes (no longer degraded) but not yet manually balanced the btrfs check crashes. After a manual balance then the btrfs check is OK.

Chris Murphy

  reply	other threads:[~2014-05-22 18:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22  2:22 mount hangs after disk crash (RAID-1) Tomasz Chmielewski
2014-05-22  8:51 ` Tomasz Chmielewski
2014-05-22 15:16   ` Tomasz Chmielewski
2014-05-22 17:50     ` Tomasz Chmielewski
2014-05-22 18:20       ` Chris Murphy [this message]
2014-05-22 21:06       ` Duncan
2014-05-22 22:07       ` Chris Murphy
2014-05-22  9:43 ` Duncan
2014-05-22 16:27   ` Chris Murphy

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).