I'm all for a more informative error message than "mkraid aborted".
Other thoughts:
1) In the kernel "make menuconfig" help, point out that this code if for an
earlier/specific version of raidtools.
2) In the Raidtools ReadMe's, make it clearer that the 2.2.x kernel's raid
options are not valid for this version. I read this document two or three
times and still didn't understand this caveat.
3) As a side issue, how about a quick blurb about using "mknod" to add
support for additional disks, since RAID'ers are likely to exceed the
default pre-setup drives. I had to setup both /dev/sdh and /dev/sdh1, and
when I put the array on the news box, its final destination, I'll have a
total of 10 drives, with a potential to go to 15.
4) I saw a note about Linux having problems with more than 16 drives, is
this the case? (aside from the fact I currently worry about overwhelming my
PCI bus...)
> -----Original Message-----
> From: Osma Ahvenlampi [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, April 21, 1999 7:14 AM
> To: Bruno Prior
> Cc: Linux-Raid; Dietmar Stein; [EMAIL PROTECTED]; Jason Speckman
> Subject: Re: Help with mirroring and Re: Raid 0 - mkraid aborted...
>
>
> "Bruno Prior" <[EMAIL PROTECTED]> writes:
> > The fact that the linux source includes legacy raid code which
> is incompatible with
> > the latest raidtools seems to cause a lot of misunderstandings.
> Can't the legacy
> > stuff be taken out and turned into a patch for those who like
> the older tools?
>
> I understood the current alpha code is scheduled for integration into
> the base kernel soon. However, if the error diagnostics of the
> raidtools were a bit better, we wouldn't have this question pop up all
> the time. "mkraid aborted" doesn't tell anyone anything. "protocol
> error, upgrade kernel raid support" would be much more informative.
>
> --
> Osma Ahvenlampi
>
