From: Michael Tokarev <mjt@tls.msk.ru>
To: Michael Guntsche <mike@it-loops.com>
Cc: linux-raid@vger.kernel.org, Robin Hill <robin@robinhill.me.uk>
Subject: Re: Strange RAID-5 rebuild problem
Date: Sun, 02 Mar 2008 13:09:36 +0300 [thread overview]
Message-ID: <47CA7CE0.9050702@msgid.tls.msk.ru> (raw)
In-Reply-To: <244F7F54-081B-462E-A0AD-8E5E1056B90B@it-loops.com>
Michael Guntsche wrote:
>
[]
> Answering myself here after reading through the manapges, this seems to
> be a regression. Furthermore this may yield to some nasty data
> corruption, well at least I think it will.
>
> * --stop the array while resyncing.
> * set start_ro to 1
> * Start the array, automatic reconstruction does not start even after
> the data is been written to the ARRAY
You can't write any data to a read-only array.
/mjt
> * stop the array again
> * set start_ro to 0
> * Start the array again
> The array picks up the resync process where it stopped the first time
> even if there has already been data written to it, while it was started
> with start_ro = 1.
> Won't this yield corrupted data, since data BEFORE that offset might
> actually have changed in the mean time?
>
> Kind regards,
> Michael
next prev parent reply other threads:[~2008-03-02 10:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 21:09 Strange RAID-5 rebuild problem Michael Guntsche
2008-03-01 22:02 ` Michael Guntsche
[not found] ` <20080301222326.GA20435@cthulhu.home.robinhill.me.uk>
2008-03-01 22:41 ` Michael Guntsche
2008-03-02 7:38 ` Michael Guntsche
2008-03-02 8:14 ` Michael Guntsche
2008-03-02 10:09 ` Michael Tokarev [this message]
2008-03-02 10:20 ` Michael Guntsche
2008-03-03 0:33 ` Neil Brown
2008-03-03 12:38 ` Michael Guntsche
2008-03-02 12:29 ` Robin Hill
2008-03-02 20:55 ` Michael Guntsche
2008-03-03 17:53 ` Bill Davidsen
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=47CA7CE0.9050702@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-raid@vger.kernel.org \
--cc=mike@it-loops.com \
--cc=robin@robinhill.me.uk \
/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).