On Fri, 16 Apr 2010, Andre Noll wrote:
> On 08:52, Andrew Vasquez wrote:
> > The driver here is simply reporting that the a command's timeout value
> > had been exceeded and the mid-layer began error-recovery with a request
> > to 'abort' the command. The abort-request completed successfully:
> >
> > qla2xxx 0000:06:09.0: scsi(0:0:0): Abort command issued -- 1 fa6a73 2002.
> >
> > I can't explain why the storage did not complete the request in the
> > allotted time.
>
> Ah, that's valuable information, thanks. The underlying Infortrend
> Raid System is rather old but worked without any problems for several
> years. We recently replaced its 400G disks by new 2T WD disks. Maybe
> the new disks have longer response times, could that be the reason? And
> is there a way to increase the timeout value?
To update the default timeout value (30 seconds) for commands
submitted to /dev/sdn to 60 seconds:
$ echo 60 > /sys/block/sdn/device/timeout
-- av
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
