linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: James Peverill <jamespev@net1plus.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Resize on dirty array?
Date: Wed, 09 Aug 2006 22:17:29 +0100	[thread overview]
Message-ID: <44DA50E9.5040309@dgreaves.com> (raw)
In-Reply-To: <44D9E41C.4050608@net1plus.com>

No, it wasn't *less* reliable than a single drive; you benefited as soon as a
James Peverill wrote:
> 
> In this case the raid WAS the backup... however it seems it turned out
> to be less reliable than the single disks it was supporting.  In the
> future I think I'll make sure my disks have varying ages so they don't
> fail all at once.
> 
be at the moment. With RAID you then stressed the remaining drives to the point
of a second failure (not that you had much choice - you *could* have spent money

> James
> 
>>> RAID is no excuse for backups.
on enough media to mirror your data whilst you played with your only remaining

I can't see where you mention the kernel version you're running? md can perform
validation sync's on a periodic basis in later kernels - Debian's mdadm enables
this in cron.

copy - that's a cost/risk tradeoff you chose not to make. I've made the same
choice in the past - I've been lucky - you were not - sorry.)

> PS: <ctrl><pgup>
> -
David

> 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
> 
drive failed. At that point you would have been just as toasted as you may well


PS
Reorganise lines from distributed reply as you like :)

-- 

  reply	other threads:[~2006-08-09 21:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08  0:36 Resize on dirty array? James Peverill
2006-08-08  0:46 ` Neil Brown
2006-08-08 19:25   ` James Peverill
2006-08-09  4:09     ` Neil Brown
2006-08-09 11:28       ` James Peverill
2006-08-09 11:37         ` Martin Schröder
2006-08-09 13:05           ` Mark Hahn
2006-08-09 13:33             ` James Peverill
2006-08-09 21:17               ` David Greaves [this message]
2006-08-10 17:44               ` dean gaudet
2006-08-12  1:11                 ` David Rees
     [not found]                 ` <72dbd3150608111810m4e4a2e07r5ddcee2132dd6d9a@mail.gmail.com>
     [not found]                   ` <Pine.LNX.4.64.0608111813250.29322@twinlark.arctic.org>
2006-08-12  2:05                     ` David Rees
2006-08-12  4:36                       ` Brad Campbell
2006-08-13 16:02                       ` dean gaudet
2006-08-30  7:30                         ` dean gaudet
2006-08-11 17:34             ` John Stoffel
2006-08-09 14:56         ` Henrik Holst
2006-08-12  7:22         ` Tuomas Leikola
2006-08-28  4:55           ` Neil Brown
2006-08-28  6:36             ` Mario 'BitKoenig' Holbe

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=44DA50E9.5040309@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=jamespev@net1plus.com \
    --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).