From: "D. Spindel" <spider@skuggor.se>
To: cwillu <cwillu@cwillu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: raid 10 corruption from single drive failure
Date: Mon, 01 Jul 2013 12:16:38 +0200 [thread overview]
Message-ID: <1372673798.3030.2.camel@Waves.darkmere> (raw)
In-Reply-To: <CAE5mzvhhMZGg7=Wy8CGZPzy93emHBNg+mqhjfo9GWmjvMBrSug@mail.gmail.com>
On lör, 2013-06-29 at 03:08 -0600, cwillu wrote:
>
> Not sure I entirely follow: mounting with -o degraded (not -o
> recovery) is how you're supposed to mount if there's a disk missing.
What I'm wondering about is why btrfsck segfaults, why it won't claim
which drive is supposedly "corrupt" in a data-loss case. In this case
the drive was present, at least the first superblock should be readable,
but I get these somewhat strange issues.
Re-sending as I forgot CC.
( Curse you, evolution )
//D.S.
prev parent reply other threads:[~2013-07-01 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 7:55 raid 10 corruption from single drive failure D. Spindel
2013-06-29 9:08 ` cwillu
2013-07-01 10:16 ` D. Spindel [this message]
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=1372673798.3030.2.camel@Waves.darkmere \
--to=spider@skuggor.se \
--cc=cwillu@cwillu.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).