linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: mount hangs after disk crash (RAID-1)
Date: Thu, 22 May 2014 16:07:58 -0600	[thread overview]
Message-ID: <ED54B94A-528B-4382-9D1F-EE8D234F55D6@colorremedies.com> (raw)
In-Reply-To: <20140522185025.4c72aab9@s9>


On May 22, 2014, at 11:50 AM, Tomasz Chmielewski <tch@virtall.com> 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?

How much metadata is there on the volume? And how much memory does the system have? This might also be a case where it might take hours, or longer, for it sort things out, and isn't actually permanently hung up. Worth a shot to leave it overnight and see what happens.

I agree trying skip_balance is worth a shot also.


Chris Murphy

  parent reply	other threads:[~2014-05-22 22:08 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
2014-05-22 21:06       ` Duncan
2014-05-22 22:07       ` Chris Murphy [this message]
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:
  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=ED54B94A-528B-4382-9D1F-EE8D234F55D6@colorremedies.com \
    --to=lists@colorremedies.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).