>>>>> On Tue, 11 Apr 2000, "Lance" == D. Lance Robinson wrote:
Lance> So, if the md driver doesn't fail a drive that is because the lower
Lance> levels have taken care of all the nitty details and have supposedly
Lance> performed the requested data transfer correctly. As long as the actual
Lance> device drivers do the requests, the md driver won't know about any
Lance> problems.
Thank-you for this explanation. The state of the array leads me to suspect
that the IDE layer was NOT "doing the right thing" and was never getting those
writes properly flushed, but I really cannot say this with any confidence.
Clearly the "write beyond end of device" followed by all my disks being kicked
from the array is indicating something badly wrong, but I'm on the fence in
regards labelling this as a hardware or a software problem.
+> 4. is there some way to mark this disk bad right now, so that
+> reconstruction is carried out from the disks I trust? I do have a hot
+> spare . . .
Lance> You can use the 'raidhotremove' utility.
This has never worked for me when the disk had not been marked as faulty by
the RAID subsystem. Just says the disk is bizzy. That's why I was looking to
set it faulty.
Thanks for the reply!
-d
