From: Neil Brown <neilb@suse.de>
To: Dexter Filmore <Dexter.Filmore@gmx.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID6 fallen apart
Date: Mon, 28 Aug 2006 22:28:17 +1000 [thread overview]
Message-ID: <17650.57697.725755.359936@cse.unsw.edu.au> (raw)
In-Reply-To: message from Dexter Filmore on Monday August 28
On Monday August 28, Dexter.Filmore@gmx.de wrote:
> Am Montag, 28. August 2006 04:03 schrieben Sie:
> > The easiest thing to do is simply recreate the array, making sure to
> > have the drives in the correct order, and any options (like chunk
> > size) the same. This will not hurt the data (if done correctly).
>
> First time I hear this. Good to know.
> Thought recreate implies sync.
It does. But 'sync' doesn't destroy data. It just updates parity
information.
NeilBrown
next prev parent reply other threads:[~2006-08-28 12:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 23:38 RAID6 fallen apart Wagner Ferenc
2006-08-28 2:03 ` Neil Brown
2006-08-28 12:20 ` Dexter Filmore
2006-08-28 12:28 ` Neil Brown [this message]
2006-08-28 15:36 ` Ferenc Wagner
2006-08-29 2:01 ` Neil Brown
2006-09-03 15:18 ` Tuomas Leikola
2006-09-03 15:19 ` Tuomas Leikola
2006-09-04 16:03 ` Ferenc Wagner
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=17650.57697.725755.359936@cse.unsw.edu.au \
--to=neilb@suse.de \
--cc=Dexter.Filmore@gmx.de \
--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).