linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Davis <alex14641@yahoo.com>
To: David Greaves <david@dgreaves.com>, Kasper Sandberg <lkml@metanurb.dk>
Cc: David Rees <drees76@gmail.com>, David Lethe <david@santools.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: Fri, 2 May 2008 15:04:55 -0700 (PDT)	[thread overview]
Message-ID: <977930.28629.qm@web50212.mail.re2.yahoo.com> (raw)
In-Reply-To: <1209764630.7827.15.camel@localhost>

--- On Fri, 5/2/08, Kasper Sandberg <lkml@metanurb.dk> wrote:

> From: Kasper Sandberg <lkml@metanurb.dk>
> Subject: Re: Sharing disks amoung multiple software RAIDs
> To: "David Greaves" <david@dgreaves.com>
> Cc: "David Rees" <drees76@gmail.com>, "David Lethe" <david@santools.com>, alex14641@yahoo.com, "Justin Piszcz" <jpiszcz@lucidpixels.com>, linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
> Date: Friday, May 2, 2008, 5:43 PM
> On Fri, 2008-05-02 at 09:25 +0100, David Greaves wrote:
> > Kasper Sandberg wrote:
> > > Im not treating it as a backup, what i want, is
> to make sure that if 1
> > > disk dies, the data is still intact and ill
> hopefully be able to run
> > > with 1 disk till the newly ordered one arrives
> > Probably one of the main design objectives behind
> RAID/md
> 
> Exactly, but once people start saying: "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 begin to worry..
> 
> > 
> > > So my question remains.. Is md raid1 not suited
> for this need? would it
> > > be safer to run in non-raid1 mode and daily(maybe
> hourly) rsync
> > > everything over to the second disk?
> > 
> > md is 100% guaranteed perfect or your money back...
> > rsync is 100% guaranteed perfect or your money back...
> > your backups are 100% guaranteed perfect or your money
> back...
> > your hard drives are 100% guaranteed perfect or your
> money back...
> > your CPU and RAM are 100% guaranteed perfect or your
> money back...
> > your CPU and PSU fans are 100% guaranteed perfect or
> your money back...
> > 
> > Clearly if you want to panic over reliability you have
> lots of choices :)
> 
> I do not wish to panic, i merely wished to know if linux MD
> is believed
> to work in most cases, or believed to do all sorts of weird
> stuff when
> resyncing :)
> 
> > 
> > David
> > PS, FWIW md has saved my data* countless times over
> the past 'n' years in
> > exactly the scenario you describe.
> 
> It has also been useful to people i know, i just wished to
> be sure :)
> and as Keld Jørn Simonsen and Helge Hafting's comments
> seems to confirm,
> linux md IS nice and stable :)
> 
> and as said, what im looking for isnt an in-box backup
> solution, merely
> safety in case one disk burns :)
> 
> > 
> > *(or more accurately has saved me from having to
> restore my data)

Just to add another data point, I've been using md in RAID 5 configuration for ~3 years with dedicated USB and SATA disks 
(not mixed) and have had disks go bad, and have yet to lose 
any data. Given the 'quality' of high-capacity disks nowadays,
RAIDing them is the right thing to do.


      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

  reply	other threads:[~2008-05-02 22:04 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 [this message]
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
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=977930.28629.qm@web50212.mail.re2.yahoo.com \
    --to=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 \
    --cc=lkml@metanurb.dk \
    /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).