I think he is referring to software RAID. And yes, it is indeed a problem
that the RedHat installer cannot create nested RAIDs (at least, I too was
unable to do that, so either it's impossible, or I'm equally blind).
> This is because if the first disk fails totally, the 2nd will be used to
> boot. You also should use an initrd image to be sure all you need to get
> up is on that small mirrored partition. After that your other partitions
> can be whatever pleases you.
Also, GRUB/LILO only support booting from RAID-1 (or no RAID).
...
> >
> > Does the kernel support autostarting nested RAID partitions?
> >
Yes it does. If you have persistent superblocks on all arrays, they
*should* autostart.
If you boot from the 4G disk, does the array start properly ? Does
it start properly even if you remove your /etc/raidtab ?
Please check that you have the correct RAID levels either compiled
into your kernel, or on an initrd.
> > Is doing software 1+0 a bad idea anyway due to performance issues?
>
> It should outperform most other RAID configs under heavy load, but in most
> cases RAID-5 is fine for system which don't need the absolute highest
> performance. Note that the extra writes are queued and there are no extra
> reads unless it is in recovery mode. RAID-1 can be faster, because there
> are two copies of the data, if one drive is busy the other can be used. I
> haven't checked to see that software RAID does that correctly and gets the
> benefit.
A performance improvement went into 2.4 at some stage - all newer 2.4 kernels
will schedule reads to the mirror which has it's head nearest to where the
read should occur. This works very well in my experience.
-- ................................................................ : jakob@unthought.net : And I see the elder races, : :.........................: putrid forms of man : : Jakob Østergaard : See him rise and claim the earth, : : OZ9ABN : his downfall is at hand. : :.........................:............{Konkhra}...............: - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/