archive mirror
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <>
To: "" <>
Subject: Re: mount hangs after disk crash (RAID-1)
Date: Thu, 22 May 2014 16:16:34 +0100	[thread overview]
Message-ID: <20140522161634.054ec95f@s9> (raw)
In-Reply-To: <20140522095101.107b62e8@s9>

> > One disk in RAID-1 crashed, so powered off, changed disk, powered
> > on, trying to mount degraded.
> > 
> > Unfortunately it hangs (running 3.14.4).
> > 
> > # mount -o degraded,compress=lzo,noatime /dev/sdb4 /home (...never
> > returns...)
> 1) Just to be sure, btrfs raid1, not btrfs on md/raid1 or the like, 
> correct?

Correct, it's btrfs raid1.

> 2) Btrfs raid1 for both data and metadata, correct?

raid1 for both data and metadata.

> 3) How many devices in the btrfs raid1?

There were 2 devices.

> 4) Did you try mounting read-only?

Tried also mounting with nospace_cache, recover, ro, but all hang in a
similar way.

> Note that unlike md/raid1, btrfs raid1 won't mount writable with only
> a single device.  You must have at least two devices to mount
> writable, tho a formerly two-device raid1 with a device missing
> should mount read-only.

That's not entirely correct - it will mount with -o degraded option.

However it hangs here...

Tomasz Chmielewski

  reply	other threads:[~2014-05-22 15:16 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 [this message]
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
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 \
    --in-reply-to=20140522161634.054ec95f@s9 \ \ \

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