Motherboard: Intel SDS2
CPU: P-III 1.4
RAM: 1024MB
IDE Controller: 3Ware 7500-8
I am trying to test S/W Raid5 with 2.4.21-pre3aa1 patch
After making the raidtab and doing 'mkraid' and mount xfs FS on /dev/md1,
it was keeep showing something about 'buffer size changed from 4096 --> 512'
and back and forth and hangs.
After reset, it would not boot due to Raid failure.
After booting with 2.4.20 kernel and remove the raidtab and boot to the
2.4.21-pre3aa1 again and repeat the same, 'mkraid' halts and ps -aux shows
raid5d and raid5syncd is in RW and DW, respectively.
Is it known bug in 2.4.21-pre33aa1 kernel?
Thanks in advance.
_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus
tester7 A. wrote:
>
> Motherboard: Intel SDS2
> CPU: P-III 1.4
> RAM: 1024MB
> IDE Controller: 3Ware 7500-8
>
> I am trying to test S/W Raid5 with 2.4.21-pre3aa1 patch
> After making the raidtab and doing 'mkraid' and mount xfs FS on /dev/md1,
> it was keeep showing something about 'buffer size changed from 4096
> --> 512' and back and forth and hangs.
> After reset, it would not boot due to Raid failure.
>
> After booting with 2.4.20 kernel and remove the raidtab and boot to
> the 2.4.21-pre3aa1 again and repeat the same, 'mkraid' halts and ps
> -aux shows raid5d and raid5syncd is in RW and DW, respectively.
Does a 2.4.21-pre3 kernel work?
>
> Is it known bug in 2.4.21-pre33aa1 kernel?
>
>
I've seen this as well when I attempted to upgrade a system with 2
raid0, and 1 raid1 devices. It was a Intel se7500wv, 4G memory, and two
3ware 7500-8. The system works just fine with old aa's, and redhat's
2.4.18-19 kernel. I didn't have much time to spend with it, and I was
waiting to test 2.4.21-pre3 before reporting the bug.
--
There is no such thing as obsolete hardware.
Merely hardware that other people don't want.
(The Second Rule of Hardware Acquisition)
Sam Flory <[email protected]>