On 11-Apr-01 at 16:39:16 Bob Glamm wrote:
> True, but that's not the root cause of the problem. I saw this
> message about two months ago - it turns out that there is an
> inconsistency between software RAID and extended/logical partitions
> on a device. Trying to do software RAID over anything but primary
> partitions results in exactly the message he sees.
>
> Yes, booting with root=/dev/md0 with both partitions in the mirror running
> does eliminate the error message from e2fsck. However, booting
> with root=/dev/md0 with one drive failed using extended partitions
> will also generate the error messages he sees, which is not what you
> want to have happen when one drive fails.
>
Thanks for this, but oh dear. In my case I can probably move hda5/hdc5 to
primary partitions, but obviously it doesn't help much if I want to mirror
various other partitions which will have to be extended ones.
> I sent this report to the Software RAID FAQ maintainer awhile ago;
> I don't know if it has made it in there yet.
>
I'd say it didn't (yet).
John.
------------------------------------------------------------------------
John Horne, University of Plymouth, UK Tel: +44 (0)1752 233914
E-mail: [EMAIL PROTECTED]
PGP key available from public key servers
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
