| 1 |
There is a huge difference between RAID5 and RAID10. |
| 2 |
|
| 3 |
Software-RAID5 should be avoided as it is CPU intensive and there are many |
| 4 |
good true hardware solutions for it that are supported in Linux. |
| 5 |
|
| 6 |
|
| 7 |
On Fri, 2 Sep 2005, Francisco Perez wrote: |
| 8 |
|
| 9 |
> Date: Fri, 02 Sep 2005 20:24:44 -0500 |
| 10 |
> From: Francisco Perez <fperez@×××××××××××.com> |
| 11 |
> Reply-To: gentoo-amd64@l.g.o |
| 12 |
> To: gentoo-amd64@l.g.o |
| 13 |
> Subject: Re: [gentoo-amd64] Upgrading to Raid |
| 14 |
> |
| 15 |
> Correct me if I am wrong since I have yet to have to deal with restoring |
| 16 |
> failed disk in an array, but in a hardware raid, with my card I would just |
| 17 |
> enter the card's bios after rebooting and then restore the new replacement |
| 18 |
> drive from the secondary image (remember I am using raid 10 with 4 disks.) |
| 19 |
> Is there something I'm forgetting? |
| 20 |
> |
| 21 |
> Frank |
| 22 |
> |
| 23 |
> Florian D. wrote: |
| 24 |
>> because there are so many people praising software-raid, you´ll probably |
| 25 |
>> find this story interesting, which happened to me yesterday (my system is |
| 26 |
>> -for the biggest part- on a raid5 partition): |
| 27 |
>> |
| 28 |
>> while I emerged koffice, played some mp3´s and let matlab calculate sth. |
| 29 |
>> in the background, I tried to start a windows program with wine. I really |
| 30 |
>> shouldn´t do that, because Linux crashed and after a hard reboot it could |
| 31 |
>> not boot any more. It stopped during the execution of the init-scripts and |
| 32 |
>> i was not able to do anything, thus: 2nd hard reboot. I have another(old) |
| 33 |
>> gentoo installation on my computer and this time I booted into that one. |
| 34 |
>> By accident I realized that one of the discs of my raid system has been |
| 35 |
>> marked as faulty and it was syncing in the background. /proc/mdstat said |
| 36 |
>> that it would need 20min or so, but after 15min it said 200min! After |
| 37 |
>> another 10min it was sth >300min (and a lot of IO errors). So I rebooted |
| 38 |
>> again, this time it synced successfully in 12min. Then it was possible to |
| 39 |
>> boot and work with my normal system without any further difficulties or IO |
| 40 |
>> errors. |
| 41 |
>> |
| 42 |
>> Summing up, I can say: |
| 43 |
>> |
| 44 |
>> + I successfully wrecked my file system, but software raid was able to |
| 45 |
>> repair it |
| 46 |
>> - without a second Linux-installation on another partition, you´re lost |
| 47 |
>> - restoring of a faulty raid disk is not reliable |
| 48 |
>> - it seems that it is not possible to boot or work with a system, whose |
| 49 |
>> system disk is being restored at the same time (Linux-2.6.12.6) |
| 50 |
> |
Archives