On Thu, Aug 07, 2008 at 11:41:59AM +0200, Harald Dunkel wrote: > Ariane van der Steldt wrote: > > > > Your best bet is to replace the disk. 30 minutes wait time seems a bit > > odd though. I have a similar situation where one disk is having > > problems, requiring the disk to restart, but that only takes approx. a > > minute. You can mark the disk as bad and replace it before the other > > disk fails I guess (after all, there's not much point in relying on a > > faulty disk). > > > > The problem is not replacing the disk, but how to avoid > 30 minutes downtime due to some low level kernel routine > getting stuck.
Mark it as a bad disk? If you do that, the raid code should do no more requests to the disk. Ariane
