Re: [PATCH] scsi_lib.c: continue after MEDIUM_ERROR
- From: Alan <alan@xxxxxxxxxxxxxxxxxxx>
- Date: Fri, 2 Feb 2007 14:50:03 +0000
your system requirements are, what the system is trying to do (i.e.,
when trying to recover a failing but not dead yet disk, IO errors should
be as quick as possible and we should choose an IO scheduler that does
not combine IO's).
If this is the right strategy for disk recovery for a given type of
device then this ought to be an automatic strategy. Most end users will
not have the knowledge to frob about in sysfs, and if the bad sector hits
at the wrong moment a sensible automatic recovery strategy is going to do
the right thing faster than human intervention, which may be some hours
away.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] scsi_lib.c: continue after MEDIUM_ERROR
- From: Mark Lord
- Re: [PATCH] scsi_lib.c: continue after MEDIUM_ERROR
- References:
- Re: [PATCH] scsi_lib.c: continue after MEDIUM_ERROR
- From: Mark Lord
- Re: [PATCH] scsi_lib.c: continue after MEDIUM_ERROR
- From: James Bottomley
- Re: [PATCH] scsi_lib.c: continue after MEDIUM_ERROR
- From: Ric Wheeler
- Re: [PATCH] scsi_lib.c: continue after MEDIUM_ERROR
- Prev by Date: Re: Slower CPU frequency reported by the kernel
- Next by Date: Re: 2.6.20-rc6-mm3
- Previous by thread: Re: [PATCH] scsi_lib.c: continue after MEDIUM_ERROR
- Next by thread: Re: [PATCH] scsi_lib.c: continue after MEDIUM_ERROR
- Index(es):
Relevant Pages
|
