linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: "Måns Rullgård" <mru@inprovide.com>
Cc: David Greaves <david@dgreaves.com>,
	Guy <bugzilla@watkins-home.com>,
	linux-raid@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: RAID5 - 2nd drive died whilst waiting for RMA
Date: Wed, 17 Nov 2004 15:44:04 +0400	[thread overview]
Message-ID: <419B3984.4060601@wasp.net.au> (raw)
In-Reply-To: <yw1x4qjog1lf.fsf@ford.inprovide.com>

Måns Rullgård wrote:
> David Greaves <david@dgreaves.com> writes:
> 
> 
>>I've been tracking this on the ide list and I've been nervous of
>>applying anything since I don't have proper  backups. I'm relying on
>>redundancy.
> 
>
> RAID can *never* replace proper backups.  RAID only protects against
> low-level disk failures.  Filesystem corruption caused by bugs,
> accidental deleting of files, etc. are happily allowed.  Get a DVD
> burner, you'll thank yourself one day.
> 

Heh. I have 2.5TB here. Thats a lot of DVD's.
I have the whole lot set chmod a-w and rely on RAID to keep me alive. (Having said it is a home 
entertainment system and would not cause mega dollar industrial damage if I lost it). All my 
original media is about 9,000km away but I could survive until I re-ripped it.

I slide my array drives out and slide in some throwaway spares to beat on for testing before I 
deploy a new kernel.

David Greaves wrote:

> 
> I looked to see what I'd need to do and given I'm running 2.6.9 I take it I'd have to apply:
>  
> http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.9-libata1-dev1.patch.bz2
> which depends on
>  
> http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.9-libata1.patch.bz2
> 
> That seems like quite a lot and I'm not clear on the level of stability impact on my system.
> 
> Now although I track linux-ide I doubt I'm fully informed!!
> So if anyone would like to inform me of a reasonable course of action then I'm actually reasonably happy to apply the SMART patch.

That is pretty close. I actually just cloned the kernel bk tree and pulled both of Jeffs trees, but 
then I ran about 10 hours of super intensive tests with 5 spare drives spread across my 3 
controllers before I slid my 13 raid disks back in and let it loose. I guess my real kernel version 
is somewhere around 2.6.10-rc1-bk3.

Have had good luck with it over the last couple of weeks and I have been hitting it pretty hard. 
But, as I said before, I'm on a UP machine. Andy pointed out some possible issues on SMP so beware 
there.

Brad
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2004-11-17 11:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-12 10:07 RAID5 - 2nd drive died whilst waiting for RMA David Greaves
2004-11-12 12:17 ` David Greaves
2004-11-12 16:22   ` Dick Streefland
2004-11-12 17:31     ` David Greaves
2004-11-12 17:49       ` Guy
2004-11-12 18:13         ` David Greaves
2004-11-12 17:48   ` Guy
2004-11-12 18:09   ` Guy
2004-11-12 18:30     ` David Greaves
2004-11-12 18:47       ` Guy
2004-11-13 19:48         ` David Greaves
2004-11-13 20:01           ` Måns Rullgård
2004-11-13 20:28             ` David Greaves
2004-11-13 20:32               ` Måns Rullgård
2004-11-13 20:39           ` Guy
2004-11-13 21:54             ` David Greaves
2004-11-15 16:55               ` David Greaves
2004-11-16  6:13                 ` Brad Campbell
2004-11-17 11:21                   ` David Greaves
2004-11-17 11:24                     ` Måns Rullgård
2004-11-17 11:44                       ` Brad Campbell [this message]
2004-11-17 12:04                       ` David Greaves
2004-11-15 20:56 ` Robin Bowes
2004-11-15 21:24   ` Guy
2004-11-15 21:30     ` Robin Bowes
2004-11-15 21:39     ` Gordon Henderson

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=419B3984.4060601@wasp.net.au \
    --to=brad@wasp.net.au \
    --cc=bugzilla@watkins-home.com \
    --cc=david@dgreaves.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mru@inprovide.com \
    /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).