From: Hugo Mills <hugo@carfax.org.uk>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btr fs unmountable after disk failure
Date: Fri, 13 Apr 2012 11:58:22 +0100 [thread overview]
Message-ID: <20120413105822.GF4856@carfax.org.uk> (raw)
In-Reply-To: <alpine.LNX.2.01.1204131252070.26191@frira.zrqbmnf.qr>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
On Fri, Apr 13, 2012 at 12:55:43PM +0200, Jan Engelhardt wrote:
>
> I originally created a RAID1(0) compound out of 4 drives. One of them
> [sdf] failed recently and was removed. The filesystem is no longer
> mountable with the 3 drives left.
> On 3.3.1:
>
> # btrfs dev scan
> [ 1065.572938] device label srv devid 1 transid 11386 /dev/sdc
> [ 1065.573044] device label srv devid 3 transid 11386 /dev/sde
> [ 1066.089981] device label srv devid 2 transid 11386 /dev/sdd
> # mount /dev/sdd /top.srv
> [ 1070.201339] device label srv devid 2 transid 11386 /dev/sdd
> [ 1070.201666] btrfs: disk space caching is enabled
> [ 1070.203310] btrfs: failed to read the system array on sde
> [ 1070.204458] btrfs: open_ctree failed
> (Sparse error message, innit..)
I think you need "-o degraded" in this case.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Mixing mathematics and alcohol is dangerous. Don't ---
drink and derive.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2012-04-13 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 10:55 btr fs unmountable after disk failure Jan Engelhardt
2012-04-13 10:58 ` Hugo Mills [this message]
2012-04-13 12:00 ` Chris Samuel
2012-04-13 13:42 ` Jan Engelhardt
2012-04-13 20:32 ` 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=20120413105822.GF4856@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=jengelh@medozas.de \
--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).