Hello all,
I'm experiencing two problems and hope that someone might be able to
shed some light. This is using 19990309-2.0.36 (and 2.2.3).
The first, I believe is a bug. I had a RAID5 partition set up and
then decided to re-allocate the disks for a raid0 configuration.
I successfully created the RAID0 device, created a file system, and
copied some files over. I then shut down the md device, and rebooted.
Upon reboot, the auto-start mechanism in the kernel still found raid5
superblocks and attempted to bring it up, but failed. It appears
to me that under a raid0 configuration the raid superblocks are not
being saved durng a raidstop. For kicks I created a raid1 device using
the same disks and that did remove the raid5 configuration, but then
I re-created the raid0 device and after reboot the auto-start mechanism
tries to bring it up as raid1. I am using ALL the disks for these devices,
so there shouldn't be any "old" disks out there from a previous raid set.
The second problem is with system hangs while using raid5. I did tweak
raidtools and the kernel source to allow up to 14 disks (going into the
reserved data space - hopefully I won't get in trouble later on), but
I exhibited the same problems with non-modified source/tools. The RAID5
set starts to init, but after some time (usally a few minutes) I get into
a total deadlock and have to reboot. I've checked the SCSI side of things
and everything appears to be in order, and I have yet to get the system to
lock up under RAID0. I haven't tried creating a small raid5 set - 3 disks,
etc.. that will be my next experiment. (I was trying to use 14 9.1gb disks).
Comments, suggestions?
Going to sleep,
Andrew <[EMAIL PROTECTED]>
