Gordon Henderson <[EMAIL PROTECTED]> writes:
> 2 problems though - I powered down a drive to see what happened and I got
> a spew of messages to say it was running in degraded mode, but it didn't
> actually carry on. It seemed that all accesses to the array were blocked.
Powering down the disk halts the SCSI bus. For some reason the Adaptec
driver can not figure out that the device is not going to respond to a
reset command and should be ignored. I hear that Buslogic controllers
work better in this respect. Sometimes the system recovers if you
power the disk back up again.
> I couldn't even halt the machine cleanly - had to hit the reset button (it
> sat there trying to unmount the disks for a long time) Rebooted, it
> wouldn't automatically rebuild the array, but a mkraid --force-resync
> seemed to work... (despite dire warnings that I'd lose all my data, it
> didn't lose anything during the rebuild!)
Since the entire bus was locked, the raid subsystem probably failed to
update the superblocks, and on reboot the system didn't know which
ones were up-to-date.
> The second is that I can't dump the array using the dump command! It just
> seems to dump the underlying directories under the mount point (usually
> nothing, but I found out that was what it was doing when I mounted
> /dev/md0 on /mnt and /mnt already had /mnt/s1 and /mnt/s2 from some
> earlier experiments with the drives individually) Very perplexing!
I don't quite understand what exactly you were trying. I can tell you
that dump for sure does work on a raid array. Did you try to dump the
mount-point directory or the device itself? Try "dump /dev/md0".
--
Osma Ahvenlampi
