Re: Default IDENTIFY timeout is 5000ms which is too short for enterprise disks

[AlanCui4080 <me@alancui.cc>]

On Tuesday, 21 April 2026 00:27，you wrote：
> From this it seems that it is simply the first IDENTIFY that times out.
> On the second try, it seems that the IDENTIFY passes, otherwise we would
> have seen more "revalidation failed (errno=-5)" prints for the same drive.
> 
> So, from this log alone, I don't see any problem. We will try to do IDENTIFY
> up to three times, so just a single IDENTIFY failing should not be a problem.

So at your opinion, the error is caused by a hardware failure but not kernel, 
so we should not add any quirk to relax or solve the problem, is that correct?
(I just want to confirm that how kernel will deal with this error)

> So I think the question is, at this point, can you read from the drive?
> 
> E.g.:
> # dd if=/dev/sda of=/dev/null iflag=direct bs=4K count=1

I will be blocked out of the shell for 5 secs unless the IDENTIFY succeed.

> 
> If you can read from the device, then this seem like a problem with zpool
> kicking the device off the RAID array (perhaps because it is taking longer
> than some zpool defined timeout value?), rather than a libata problem.

But after the link re-established, the drive works normally.

Alan