From: David Greaves <david@dgreaves.com>
To: Francois Barre <francois.barre@gmail.com>
Cc: "Neil Brown" <neilb@suse.de>, "Ákos Maróy" <darkeye@tyrell.hu>,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: raid issues after power failure
Date: Sun, 02 Jul 2006 10:26:18 +0100 [thread overview]
Message-ID: <44A7913A.1050409@dgreaves.com> (raw)
In-Reply-To: <fd8d0180607020114m5e02e1ek553e5da2941eb6dd@mail.gmail.com>
Francois Barre wrote:
> 2006/7/1, Ákos Maróy <darkeye@tyrell.hu>:
>> Neil Brown wrote:
>> > Try adding '--force' to the -A line.
>> > That tells mdadm to try really hard to assemble the array.
>>
>> thanks, this seems to have solved the issue...
>>
>>
>> Akos
>>
>>
>
> Well, Neil, I'm wondering,
> It seemed to me that Akos' description of the problem was that
> re-adding the drive (with mdadm not complaining about anything) would
> trigger a resync that would not even start.
> But as your '--force' does the trick, it implies that the resync was
> not really triggered after all without it... Or did I miss a bit of
> log Akos provided that did say so ?
> Could there be a place here for an error message ?
>
> More generally, could it be usefull to build up a recovery howto,
> based on the experiences on this list (I guess 90% of the posts a
> related to recoveries) ?
> Not in terms of a standard disk loss, but in terms of a power failure
> or a major disk problem. You know, re-creating the array, rolling the
> dices, and *tada !* your data is back again... I could not find a bit
> of doc about this.
>
Francois,
I have started to put a wiki in place here:
http://linux-raid.osdl.org/
My reasoning was *exactly* that - there is reference information for md
but sometimes the incantations need a little explanation and often the
diagnostics are not obvious...
I've been subscribed to linux-raid since the middle of last year and
I've been going through old messages looking for nuggets to base some
docs around.
I haven't had a huge amount of time recently so I've just scribbled on
it for now - I wanted to present something a little more polished to the
community - but since you're asking...
So don't consider this an official announcement of a useable work yet -
more a 'Please contact me if you would like to contribute' (just so I
can keep track of interested parties) and we can build something up...
David
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-07-02 9:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 9:12 raid issues after power failure Ákos Maróy
2006-06-30 9:21 ` Francois Barre
2006-06-30 9:25 ` Ákos Maróy
[not found] ` <fd8d0180606300250q6fbab5d3wdf343b530f3119a9@mail.gmail.com>
2006-06-30 9:51 ` Francois Barre
2006-06-30 9:56 ` Francois Barre
2006-06-30 12:29 ` Akos Maroy
2006-06-30 12:40 ` Francois Barre
2006-06-30 12:43 ` Akos Maroy
2006-06-30 12:57 ` Francois Barre
2006-06-30 23:06 ` Neil Brown
2006-07-01 15:28 ` Ákos Maróy
2006-07-02 8:14 ` Francois Barre
2006-07-02 9:26 ` David Greaves [this message]
2006-07-03 8:54 ` Ákos Maróy
2006-07-03 9:16 ` Francois Barre
2006-07-03 11:30 ` Ákos Maróy
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=44A7913A.1050409@dgreaves.com \
--to=david@dgreaves.com \
--cc=darkeye@tyrell.hu \
--cc=francois.barre@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).