From: Anders Widman <andewid@tnonline.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM and fault tolerance
Date: Sat, 31 Mar 2001 19:17:11 +0200 [thread overview]
Message-ID: <3AC61117.F16884CD@tnonline.net> (raw)
In-Reply-To: 0103281643400K.27902@lyta
Well. Yes. The ideal way is of course to buy more 80GB disks.
So, there is no way that linux does support rebuilding an RAID 4/5 array when
adding extra disks (of equal size)?
Thanks,
Anders
Russell Coker wrote:
> On Wednesday 28 March 2001 08:29, Anders Widman wrote:
> > ok. great... so if I make say 20GB partitions on all disks and put them
> > in a RAID-5 array. Can I add extra disks and rebuild the array? I have
> > seen some expensive RAID cards that does that.
>
> RAID-4 involves having N data disks (N >= 2) and 1 parity disk. The parity
> disk contains the XOR of the blocks on the N data disks. If one of the N
> disks dies then it's contents can easily be regenerated by the XOR of the
> surviving N-1 disks and the parity disk.
> RAID-5 is the same but has the parity data spread across all the disks for
> best performance. Thus RAID-5 has 3 or more disks.
>
> In RAID-4 or RAID-5 if you lose two disks at the same time then the XOR won't
> get your data back and you are comprehensively stuffed.
>
> If you create a RAID-5 with two partitions on the same disk then you may as
> well use a bulk eraser.
>
> The scheme I mentioned in my previous message is the simplest way of doing
> this with such disks. But really if your time is worth more than about $10
> per hour you should just buy some more 80G disks.
>
> --
> http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
> http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
> http://www.coker.com.au/projects.html Projects I am working on
> http://www.coker.com.au/~russell/ My home page
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
Russell Coker wrote:
> On Wednesday 28 March 2001 08:29, Anders Widman wrote:
> > ok. great... so if I make say 20GB partitions on all disks and put them
> > in a RAID-5 array. Can I add extra disks and rebuild the array? I have
> > seen some expensive RAID cards that does that.
>
> RAID-4 involves having N data disks (N >= 2) and 1 parity disk. The parity
> disk contains the XOR of the blocks on the N data disks. If one of the N
> disks dies then it's contents can easily be regenerated by the XOR of the
> surviving N-1 disks and the parity disk.
> RAID-5 is the same but has the parity data spread across all the disks for
> best performance. Thus RAID-5 has 3 or more disks.
>
> In RAID-4 or RAID-5 if you lose two disks at the same time then the XOR won't
> get your data back and you are comprehensively stuffed.
>
> If you create a RAID-5 with two partitions on the same disk then you may as
> well use a bulk eraser.
>
> The scheme I mentioned in my previous message is the simplest way of doing
> this with such disks. But really if your time is worth more than about $10
> per hour you should just buy some more 80G disks.
>
> --
> http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
> http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
> http://www.coker.com.au/projects.html Projects I am working on
> http://www.coker.com.au/~russell/ My home page
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
Russell Coker wrote:
> On Wednesday 28 March 2001 08:29, Anders Widman wrote:
> > ok. great... so if I make say 20GB partitions on all disks and put them
> > in a RAID-5 array. Can I add extra disks and rebuild the array? I have
> > seen some expensive RAID cards that does that.
>
> RAID-4 involves having N data disks (N >= 2) and 1 parity disk. The parity
> disk contains the XOR of the blocks on the N data disks. If one of the N
> disks dies then it's contents can easily be regenerated by the XOR of the
> surviving N-1 disks and the parity disk.
> RAID-5 is the same but has the parity data spread across all the disks for
> best performance. Thus RAID-5 has 3 or more disks.
>
> In RAID-4 or RAID-5 if you lose two disks at the same time then the XOR won't
> get your data back and you are comprehensively stuffed.
>
> If you create a RAID-5 with two partitions on the same disk then you may as
> well use a bulk eraser.
>
> The scheme I mentioned in my previous message is the simplest way of doing
> this with such disks. But really if your time is worth more than about $10
> per hour you should just buy some more 80G disks.
>
> --
> http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
> http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
> http://www.coker.com.au/projects.html Projects I am working on
> http://www.coker.com.au/~russell/ My home page
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
Russell Coker wrote:
> On Wednesday 28 March 2001 08:29, Anders Widman wrote:
> > ok. great... so if I make say 20GB partitions on all disks and put them
> > in a RAID-5 array. Can I add extra disks and rebuild the array? I have
> > seen some expensive RAID cards that does that.
>
> RAID-4 involves having N data disks (N >= 2) and 1 parity disk. The parity
> disk contains the XOR of the blocks on the N data disks. If one of the N
> disks dies then it's contents can easily be regenerated by the XOR of the
> surviving N-1 disks and the parity disk.
> RAID-5 is the same but has the parity data spread across all the disks for
> best performance. Thus RAID-5 has 3 or more disks.
>
> In RAID-4 or RAID-5 if you lose two disks at the same time then the XOR won't
> get your data back and you are comprehensively stuffed.
>
> If you create a RAID-5 with two partitions on the same disk then you may as
> well use a bulk eraser.
>
> The scheme I mentioned in my previous message is the simplest way of doing
> this with such disks. But really if your time is worth more than about $10
> per hour you should just buy some more 80G disks.
>
> --
> http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
> http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
> http://www.coker.com.au/projects.html Projects I am working on
> http://www.coker.com.au/~russell/ My home page
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
Russell Coker wrote:
> On Wednesday 28 March 2001 08:29, Anders Widman wrote:
> > ok. great... so if I make say 20GB partitions on all disks and put them
> > in a RAID-5 array. Can I add extra disks and rebuild the array? I have
> > seen some expensive RAID cards that does that.
>
> RAID-4 involves having N data disks (N >= 2) and 1 parity disk. The parity
> disk contains the XOR of the blocks on the N data disks. If one of the N
> disks dies then it's contents can easily be regenerated by the XOR of the
> surviving N-1 disks and the parity disk.
> RAID-5 is the same but has the parity data spread across all the disks for
> best performance. Thus RAID-5 has 3 or more disks.
>
> In RAID-4 or RAID-5 if you lose two disks at the same time then the XOR won't
> get your data back and you are comprehensively stuffed.
>
> If you create a RAID-5 with two partitions on the same disk then you may as
> well use a bulk eraser.
>
> The scheme I mentioned in my previous message is the simplest way of doing
> this with such disks. But really if your time is worth more than about $10
> per hour you should just buy some more 80G disks.
>
> --
> http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
> http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
> http://www.coker.com.au/projects.html Projects I am working on
> http://www.coker.com.au/~russell/ My home page
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
next prev parent reply other threads:[~2001-03-31 17:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-19 20:13 [linux-lvm] vgscan won't recognize my VG David Vidal Rodriguez
2001-03-19 20:37 ` Andreas Dilger
2001-03-20 18:52 ` David Vidal Rodriguez
2001-03-20 19:17 ` AJ Lewis
2001-03-20 19:25 ` Andreas Dilger
2001-03-20 19:35 ` David Vidal Rodriguez
2001-03-20 20:00 ` David Vidal Rodriguez
2001-03-20 20:21 ` Andreas Dilger
2001-03-20 20:36 ` David Vidal Rodriguez
2001-03-21 0:29 ` Kirth
2001-03-21 18:30 ` David Vidal Rodriguez
2001-03-21 19:17 ` Andreas Dilger
2001-03-23 14:55 ` David Vidal Rodriguez
2001-03-23 22:36 ` Andreas Dilger
2001-03-20 20:57 ` [linux-lvm] LVM and fault tolerance Anders Widman
2001-03-21 17:33 ` Lars Kellogg-Stedman
2001-03-22 23:59 ` Anders Widman
[not found] ` <0103262137020G.01456@lyta>
2001-03-27 21:48 ` Anders Widman
2001-03-27 21:56 ` Ragnar Kjørstad
2001-03-27 22:29 ` Anders Widman
2001-03-27 22:45 ` Ragnar Kjørstad
2001-03-28 6:43 ` Russell Coker
2001-03-31 17:17 ` Anders Widman [this message]
2001-03-20 20:23 ` [linux-lvm] vgscan won't recognize my VG José Luis Domingo López
2001-03-20 19:31 ` AJ Lewis
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=3AC61117.F16884CD@tnonline.net \
--to=andewid@tnonline.net \
--cc=linux-lvm@sistina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.