linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: maarten <maarten@ultratux.net>
To: linux-raid@vger.kernel.org
Subject: Re: Spares and partitioning huge disks
Date: Sat, 8 Jan 2005 17:49:32 +0100	[thread overview]
Message-ID: <200501081749.32816.maarten@ultratux.net> (raw)
In-Reply-To: <20050108145228.GB26475@janus>

On Saturday 08 January 2005 15:52, Frank van Maarseveen wrote:
> On Fri, Jan 07, 2005 at 04:57:35PM -0500, Guy wrote:
> > His plan is to split the disks into 6 partitions.
> > Each of his six RAID5 arrays will only use 1 partition of each physical
> > disk.
> > If he were to lose a disk, all 6 RAID5 arrays would only see 1 failed
> > disk. If he gets 2 read errors, on different disks, at the same time, he
> > has a 1/6 chance they would be in the same array (which would be bad).
> > His plan is to combine the 6 arrays with LVM or a linear array.
>
> Intriguing setup. Do you think this actually improves the reliability
> with respect to disk failure compared to creating just one large RAID5
> array?

Yes.  But I get no credits; someone else here invented the idea.

> For one second I thought it's a clever trick but gut feeling tells
> me the odds of losing the entire array won't change (simplified --
> because the increased complexity creates room for additional errors).

No.  It is somewhat more complex, true, but no different than making, for 
example, 6 md arrays for six different mountpoints. And I just add all six 
together in an LVM. The idea behind it is that not all errors with md are 
fatal.  In the case of a non-fatal error, just re-adding the disk might solve 
it since the drive then will remap the bad sector.  However, IF during that 
resync one other drive has a read error, it gets kicked too and the array 
dies.  The chances of that happening are not very small; during resync all of 
the other drives get read in whole, so that is much more intensive than 
normal operation. So at the precise moment you really can't afford to get a 
read error, the chances of getting one are greater than ever(!). 

By dividing the physical disk in smaller parts one decreases the chance of a 
second disk with a bad sector being on the same array. You could have 3 or 
even 4 disks with bad sectors without losing the array, provided you're lucky 
and they all are on different parts of the drive platters (precisely: in 
different arrays). This is in theory of course, you'd be stupid to leave an 
array degraded and let chance decide which one breaks next... ;-)

Besides this, the resync time in case of a fault decreases by a factor 6 too 
as an added bonus. I don't know about you but over here resyncing a 250GB 
disk takes the better part of the day. (To be honest, that was a slow system)

Now it is certain that you'll strike a compromise between the added complexity 
and the benefits of this setup, so you choose an arbitrary amount of md 
arrays to define. For me six seemed okay, there is no need to go overboard 
and define real small arrays like 10 GB ones (24 of them).  ;-)

Maarten



  parent reply	other threads:[~2005-01-08 16:49 UTC|newest]

Thread overview: 94+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 14:16 Spares and partitioning huge disks maarten
2005-01-06 16:46 ` Guy
2005-01-06 17:08   ` maarten
2005-01-06 17:31 ` Guy
2005-01-06 18:18   ` maarten
     [not found]     ` <41DD83DA.9040609@h3c.com>
2005-01-06 19:42       ` maarten
2005-01-07 20:59 ` Mario Holbe
2005-01-07 21:57   ` Guy
2005-01-08 10:22     ` Mario Holbe
2005-01-08 12:19       ` maarten
2005-01-08 16:33         ` Guy
2005-01-08 16:58           ` maarten
2005-01-08 14:52     ` Frank van Maarseveen
2005-01-08 15:50       ` Mario Holbe
2005-01-08 16:32       ` Guy
2005-01-08 17:16         ` maarten
2005-01-08 18:55           ` Guy
2005-01-08 19:25             ` maarten
2005-01-08 20:33               ` Mario Holbe
2005-01-08 23:01                 ` maarten
2005-01-09 10:10                   ` Mario Holbe
2005-01-09 16:23                     ` Guy
2005-01-09 16:36                       ` Michael Tokarev
2005-01-09 17:52                         ` Peter T. Breuer
2005-01-09 17:59                           ` Michael Tokarev
2005-01-09 18:34                             ` Peter T. Breuer
2005-01-09 20:28                             ` Guy
2005-01-09 20:47                               ` Peter T. Breuer
2005-01-10  7:19                                 ` Peter T. Breuer
2005-01-10  9:05                                   ` Guy
2005-01-10  9:38                                     ` Peter T. Breuer
2005-01-10 12:31                                   ` Peter T. Breuer
2005-01-10 13:19                                     ` Peter T. Breuer
2005-01-10 18:37                                       ` Peter T. Breuer
2005-01-11 11:34                                         ` Peter T. Breuer
2005-01-08 23:09               ` Guy
2005-01-09  0:56                 ` maarten
2005-01-13  2:05                 ` Neil Brown
2005-01-13  4:55                   ` Guy
2005-01-13  9:27                   ` Peter T. Breuer
2005-01-13 15:53                     ` Guy
2005-01-13 17:16                       ` Peter T. Breuer
2005-01-13 20:40                         ` Guy
2005-01-13 23:32                           ` Peter T. Breuer
2005-01-14  2:43                             ` Guy
2005-01-08 16:49       ` maarten [this message]
2005-01-08 19:01         ` maarten
2005-01-10 16:34           ` maarten
2005-01-10 16:36             ` Gordon Henderson
2005-01-10 17:10               ` maarten
2005-01-16 16:19                 ` 4 questions. Chieftec chassis case CA-01B, resync times, selecting ide driver module loading, raid5 :2 drives on same ide channel Mitchell Laks
2005-01-16 17:53                   ` Gordon Henderson
2005-01-16 18:22                   ` Maarten
2005-01-16 19:39                   ` Guy
2005-01-16 20:55                     ` Maarten
2005-01-16 21:58                       ` Guy
2005-01-10 17:13             ` Spares and partitioning huge disks Guy
2005-01-10 17:35               ` hard disk re-locates bad block on read Guy
2005-01-11 14:34                 ` Tom Coughlan
2005-01-11 22:43                   ` Guy
2005-01-12 13:51                     ` Tom Coughlan
2005-01-10 18:24               ` Spares and partitioning huge disks maarten
2005-01-10 20:09                 ` Guy
2005-01-10 21:21                   ` maarten
2005-01-11  1:04                   ` maarten
2005-01-10 18:40               ` maarten
2005-01-10 19:41                 ` Guy
2005-01-12 11:41               ` RAID-6 Gordon Henderson
2005-01-13  2:11                 ` RAID-6 Neil Brown
2005-01-15 16:12                   ` RAID-6 Gordon Henderson
2005-01-17  8:04                     ` RAID-6 Turbo Fredriksson
2005-01-11 10:09             ` Spares and partitioning huge disks KELEMEN Peter
2005-01-09 19:33         ` Frank van Maarseveen
2005-01-09 21:26           ` maarten
2005-01-09 22:29             ` Frank van Maarseveen
2005-01-09 23:16               ` maarten
2005-01-10  8:15                 ` Frank van Maarseveen
2005-01-14 17:29                   ` Dieter Stueken
2005-01-14 17:46                     ` maarten
2005-01-14 19:14                       ` Derek Piper
2005-01-15  0:13                     ` Michael Tokarev
2005-01-15  9:34                       ` Peter T. Breuer
2005-01-15  9:54                         ` Mikael Abrahamsson
2005-01-15 10:31                           ` Brad Campbell
2005-01-15 11:10                             ` Mikael Abrahamsson
2005-01-15 10:33                           ` Peter T. Breuer
2005-01-15 11:07                             ` Mikael Abrahamsson
2005-01-09 23:20             ` Guy
2005-01-10  7:42               ` Gordon Henderson
2005-01-10  9:03                 ` Guy
2005-01-10 12:21                   ` Stats... [RE: Spares and partitioning huge disks] Gordon Henderson
2005-01-10  0:42             ` Spares and partitioning huge disks Guy
  -- strict thread matches above, loose matches on Subject: below --
2005-01-13  9:53 Bene Martin
2005-01-13 10:11 ` Peter T. Breuer

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=200501081749.32816.maarten@ultratux.net \
    --to=maarten@ultratux.net \
    --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).