From: Doug Ledford <dledford@redhat.com>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: linux-raid mailing list <linux-raid@vger.kernel.org>
Subject: Re: avoiding the initial resync on --create
Date: Mon, 09 Oct 2006 12:32:00 -0400 [thread overview]
Message-ID: <1160411520.2917.76.camel@fc6.xsintricity.com> (raw)
In-Reply-To: <20061009134946.GA26122@harddisk-recovery.com>
[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]
On Mon, 2006-10-09 at 15:49 +0200, Erik Mouw wrote:
> There is no way to figure out what exactly is correct data and what is
> not. It might work right after creation and during the initial install,
> but after the next reboot there is no way to figure out what blocks to
> believe.
You don't really need to. After a clean install, the operating system
has no business reading any block it didn't write to during the install
unless you are just reading disk blocks for the fun of it. And any
program that depends on data that hasn't first been written to disk is
just wrong and stupid anyway.
> > Do you have any thoughts on the issue? If Debian were to --create
> > its arrays with --assume-clean just before slapping a filesystem on
> > them and installing the system, do you see any potential problems?
>
> If you want to speed up the initial install, I'd say it's better to
> create the array with one missing drive, install the system and let it
> resync upon the next boot. Be sure to tell the user about that, though.
>
>
> Erik
>
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: CFBFF194
http://people.redhat.com/dledford
Infiniband specific RPMs available at
http://people.redhat.com/dledford/Infiniband
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-09 16:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 12:57 avoiding the initial resync on --create martin f krafft
2006-10-09 13:49 ` Erik Mouw
2006-10-09 16:32 ` Doug Ledford [this message]
2006-10-09 19:10 ` Rob Bray
2006-10-09 19:45 ` Doug Ledford
2006-10-09 21:33 ` Neil Brown
2006-10-09 21:45 ` Doug Ledford
2006-10-09 23:14 ` Neil Brown
2006-10-11 21:24 ` Michael Tokarev
2006-10-10 9:55 ` Gabor Gombas
2006-10-10 17:47 ` Doug Ledford
2006-10-10 19:18 ` Sergey Vlasov
2006-10-10 20:38 ` Doug Ledford
2006-10-10 20:37 ` Gabor Gombas
2006-10-10 21:26 ` Doug Ledford
2006-10-10 22:14 ` Rev. Jeffrey Paul
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=1160411520.2917.76.camel@fc6.xsintricity.com \
--to=dledford@redhat.com \
--cc=erik@harddisk-recovery.com \
--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).