Andreas Kostyrka wrote:
> Well, with patch-2.2.13pre12.gz the raid0145 patch doesn't apply cleanly
> (it detects itself as partly applied.)
The raid patch is for 2.2.11, that's why. Some corrections has been included in the
raid patch
which overlaps the same corrections in 2.2.13pre12. No harm
On Fri, 24 Sep 1999, Tomas Fasth wrote:
> Andreas Kostyrka wrote:
>
> > Well, with patch-2.2.13pre12.gz the raid0145 patch doesn't apply cleanly
> > (it detects itself as partly applied.)
>
> The raid patch is for 2.2.11, that's why. Some corrections has been included in the
>raid patch
> whic
On Fri, 24 Sep 1999, Tomas Fasth wrote:
> Andreas Kostyrka wrote:
>
> > open("/dev/md0", O_RDONLY) = 4
> > ioctl(4, 0x40480923, 0x804f748) = -1 EINVAL (Invalid argument)
>
> The above indicate that you're trying to use the new raid toolchain with
> old raid kernel support.
Andreas Kostyrka wrote:
> open("/dev/md0", O_RDONLY) = 4
> ioctl(4, 0x40480923, 0x804f748) = -1 EINVAL (Invalid argument)
The above indicate that you're trying to use the new raid toolchain with
old raid kernel support. You need to apply new raid patch on your kernel
code tr
Hi!
I've been wondering what the correct versions of raidtools are for
2.2.12 (or 2.2.12 with Alan Cox pre patch applied)?
With raidtools 0.90 (locally recompiled and RH6.0 versions), I get
[root@server SPECS]# /sbin/mkraid /dev/md0
handling MD device /dev/md0
analyzing super-block
disk 0: /dev/
