From: Kasper Sandberg <lkml@metanurb.dk>
To: David Lethe <david@santools.com>
Cc: David Greaves <david@dgreaves.com>,
David Rees <drees76@gmail.com>,
alex14641@yahoo.com, Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: RE: Sharing disks amoung multiple software RAIDs
Date: Sat, 03 May 2008 05:11:40 +0200 [thread overview]
Message-ID: <1209784300.7827.19.camel@localhost> (raw)
In-Reply-To: <A20315AE59B5C34585629E258D76A97C335960@34093-C3-EVS3.exchange.rackspace.com>
On Fri, 2008-05-02 at 17:24 -0500, David Lethe wrote:
>
> -----Original Message-----
<snip>
> > *(or more accurately has saved me from having to restore my data)
> =======================
> Since I am the person that wrote that "Look how many problems people
> post to the thread on a weekly basis where people lose their data when md rebuilds go bad with
> non-shared disks", I think need to clarify.
>
> I was being too literal. md is a good solution (I use it myself). However, the OP wanted to "Make sure that if one disk dies, the data is still in tact".
>
> Only way to do that is have a good offsite backup.
>
> Nothing can prevent opportunity for data loss. I don't care what RAID level (with single redundancy) you use or whether you have software or hardware-based RAID .. rebuilds can not reconstruct data if you are in degraded mode and have an unrecoverable read error on surviving disks. It is not md's job or design point to insure data consistency check/repairs are run 24x7. As such, by definition, there is no way to insure that a md rebuild will always be successful.
I realize this, but the original wording really sounded like more like
"well, there is a CHANCE your reconstruct will work good", rather than
"well, there is a CHANCE your reconstruct will fail", if you get what i
mean :)
Naturally there can always be errors or bugs, but the whole point (for
me) in doing the raid1, is that i will have much lower chance of loosing
my data, since a disk can suddenly die, and hopefully in this case, the
other will not. and well, an extra disk doesent really cost so much.
Thanks for the clarification :)
>
> David
> ---------
>
>
>
>
>
next prev parent reply other threads:[~2008-05-03 3:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 11:35 Sharing disks amoung multiple software RAIDs Alex Davis
2008-05-01 12:50 ` Justin Piszcz
2008-05-01 13:42 ` Alex Davis
2008-05-02 21:24 ` Bill Davidsen
2008-05-02 1:39 ` Kasper Sandberg
2008-05-02 1:51 ` Alex Davis
2008-05-02 2:31 ` David Lethe
2008-05-02 2:42 ` Kasper Sandberg
2008-05-02 7:06 ` David Rees
2008-05-02 8:09 ` Kasper Sandberg
2008-05-02 8:25 ` David Greaves
2008-05-02 21:43 ` Kasper Sandberg
2008-05-02 22:04 ` Alex Davis
2008-05-02 22:24 ` David Lethe
2008-05-03 0:44 ` Alex Davis
2008-05-03 10:13 ` Keld Jørn Simonsen
2008-05-03 3:11 ` Kasper Sandberg [this message]
2008-05-02 10:25 ` Keld Jørn Simonsen
[not found] ` <481E0726.1030501@harddata.com>
[not found] ` <20080504212927.GB20650@rap.rap.dk>
[not found] ` <481E3374.4070105@harddata.com>
2008-05-04 23:10 ` Keld Jørn Simonsen
2008-05-04 23:17 ` Keld Jørn Simonsen
2008-05-02 13:43 ` Helge Hafting
2008-05-02 14:13 ` Alex Davis
2008-05-01 12:51 ` David Greaves
2008-05-02 1:23 ` Nick Andrew
-- strict thread matches above, loose matches on Subject: below --
2008-05-02 8:36 George Spelvin
2008-05-02 11:07 ` Alex Davis
2008-05-02 13:26 ` Richard Michael
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=1209784300.7827.19.camel@localhost \
--to=lkml@metanurb.dk \
--cc=alex14641@yahoo.com \
--cc=david@dgreaves.com \
--cc=david@santools.com \
--cc=drees76@gmail.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--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).