All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Unmountable Array After Drive Failure During Device Deletion
Date: Thu, 19 Dec 2013 18:07:04 +0000 (UTC)	[thread overview]
Message-ID: <pan$a2b51$7fd8f776$b8dead2a$ea511250@cox.net> (raw)
In-Reply-To: 52B2BBE1.8090306@gmail.com

Chris Kastorff posted on Thu, 19 Dec 2013 01:26:57 -0800 as excerpted:

> I'm using btrfs in data and metadata RAID10 on drives (not on md or any
> other fanciness.)
> 
> I was removing a drive (btrfs dev del) and during that operation, a
> different drive in the array failed. Having not had this happen before,
> I shut down the machine immediately due to the extremely loud piezo
> buzzer on the drive controller card. I attempted to do so cleanly, but
> the buzzer cut through my patience and after 4 minutes I cut the power.
> 
> Afterwards, I located and removed the failed drive from the system, and
> then got back to linux. The array no longer mounts ("failed to read the
> system array on sdc"), with nearly identical messages when attempted
> with -o recovery and -o recovery,ro.

This may be a stupid question, but you're missing a drive so the 
filesystem will be degraded, but you didn't mention that in your mount 
options, so...

Did you try mounting with -o degraded (possibly with recovery, etc, also, 
but just try -o degraded plus any normal options first)?

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2013-12-19 18:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19  9:26 Unmountable Array After Drive Failure During Device Deletion Chris Kastorff
2013-12-19 18:07 ` Duncan [this message]
2013-12-19 19:16   ` Chris Kastorff
2013-12-19 19:41     ` Chris Kastorff
2013-12-19 22:21 ` Chris Murphy
2013-12-20  0:06   ` Chris Kastorff
2013-12-20  3:47     ` Chris Murphy
2013-12-21 23:16       ` Chris Kastorff
2013-12-21 23:40         ` Chris Murphy
2013-12-22  1:15 ` ronnie sahlberg
2013-12-22 11:35   ` Duncan
2013-12-26 23:18     ` Chris Samuel

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='pan$a2b51$7fd8f776$b8dead2a$ea511250@cox.net' \
    --to=1i5t5.duncan@cox.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.