linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Burgess <aab@cichlid.com>
To: LCID Fire <lcid-fire@gmx.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Recreate raid 10 array
Date: Thu, 09 Apr 2009 03:47:17 -0700	[thread overview]
Message-ID: <1239274037.23944.3.camel@cichlid.com> (raw)
In-Reply-To: <49DD21C6.4060200@gmx.net>

On Thu, 2009-04-09 at 00:14 +0200, LCID Fire wrote:

> > Most fscks can be told to run read-only so they won't write to the
> > device and also interactive so they ask before writing so you should be
> > able to avoid recopying. The ext3 journal recovery violates at least one
> > of these IIRC (or used to) so if it's ext3 find an option to tell it to
> > ignore the journal.

> Too late. The journal recovery did complain quite a bit and I didn't 
> know better than to have it fix the things it liked to fix.

Sorry to hear that. Actually our advice should have been to assemble the
array read-only, then all manner of fs bugs/features could not write to
it.

If anyone ever implements the --wild-ass-guess/--recreate mdadm option
perhaps that should automatically set read-only?


  reply	other threads:[~2009-04-09 10:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 19:49 Recreate raid 10 array LCID Fire
2009-04-07  6:13 ` Goswin von Brederlow
2009-04-08 21:47   ` Bill Davidsen
2009-04-08 21:57     ` Andrew Burgess
2009-04-08 22:13       ` Goswin von Brederlow
2009-04-08 22:14       ` LCID Fire
2009-04-09 10:47         ` Andrew Burgess [this message]
2009-04-10  1:41           ` Goswin von Brederlow
2009-04-09 22:38         ` Bill Davidsen
2009-04-10 11:01         ` LCID Fire
2009-04-10 14:25           ` LCID Fire

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=1239274037.23944.3.camel@cichlid.com \
    --to=aab@cichlid.com \
    --cc=lcid-fire@gmx.net \
    --cc=linux-raid@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).