It might be due to retrying what something (initiator or target) thinks
is a bad IO.
On 11/05/2012 06:47 AM, Ulrich Windl wrote:
> Hi!
>
> I have an update on the "ioctl() takes 16 seconds" issue:
>
> It seems (don't ask me for an explanation) if the buffer size for the SCSI
> response is too
Hi!
I have an update on the "ioctl() takes 16 seconds" issue:
It seems (don't ask me for an explanation) if the buffer size for the SCSI
response is too small (in my case less than 18 octets), the wsystemcall to read
the SCSI serial number takes 15-16 seconds, while with a buffer of 18 octets o
>>> Michael Christie schrieb am 24.09.2012 um 04:46 in
Nachricht <1f8fae71-ee7c-4785-a648-24758b18e...@cs.wisc.edu>:
> From what I can tell, it is a dm raid issue or a target issue.
>
> The len dm raid is using might not be right, but I am not sure. I do not
> know why the target does not like i
>From what I can tell, it is a dm raid issue or a target issue.
The len dm raid is using might not be right, but I am not sure. I do not know
why the target does not like it.
On Sep 21, 2012, at 5:59 AM, Ulrich Windl
wrote
>> # time sg_inq -e -p 80- /dev/sdc
>> unrecognized multiplier
>> Bad
>>
>> sg_inq -E /dev/sdc
>
> # time sg_inq -E /dev/sdc
> VPD INQUIRY: extended INQUIRY data page
> SPT=0 GRD_CHK=0 APP_CHK=0 REF_CHK=0
> UASK_SUP=0 GROUP_SUP=0 PRIOR_SUP=0 HEADSUP=0 ORDSUP=0 SIMPSUP=0
> WU_SUP=0 CRD_SUP=0 NV_SUP=1 V_SUP=1
> P_I_I_SUP=0 LUICLR=0 CBCS=0 R_SUP=0
> Multi I_T nex
