Re: [PATCH] scsi_dh_rdac: always retry MODE SELECT on command lock violation

2016-02-04 Thread Martin K. Petersen
> "Hannes" == Hannes Reinecke writes: Hannes> If MODE SELECT returns with sense '05/91/36' (command lock Hannes> violation) it should always be retried without counting the Hannes> number of retries. During an HBA upgrade or similar Hannes> circumstances one might see a flood of MODE SELECT

Re: [PATCH] scsi_dh_rdac: always retry MODE SELECT on command lock violation

2016-02-03 Thread Hannes Reinecke
On 02/04/2016 03:48 AM, Martin K. Petersen wrote: >> "Hannes" == Hannes Reinecke writes: > > Hannes> If MODE SELECT returns with sense '05/91/36' (command lock > Hannes> violation) it should always be retried without counting the > Hannes> number of retries. During an HBA upgrade or similar

Re: [PATCH] scsi_dh_rdac: always retry MODE SELECT on command lock violation

2016-02-03 Thread Martin K. Petersen
> "Hannes" == Hannes Reinecke writes: Hannes> If MODE SELECT returns with sense '05/91/36' (command lock Hannes> violation) it should always be retried without counting the Hannes> number of retries. During an HBA upgrade or similar Hannes> circumstances one might see a flood of MODE SELECT

Re: [PATCH] scsi_dh_rdac: always retry MODE SELECT on command lock violation

2016-01-22 Thread Johannes Thumshirn
On Fri, Jan 22, 2016 at 03:42:41PM +0100, Hannes Reinecke wrote: > If MODE SELECT returns with sense '05/91/36' (command lock violation) > it should always be retried without counting the number of retries. > During an HBA upgrade or similar circumstances one might see a flood > of MODE SELECT comm

[PATCH] scsi_dh_rdac: always retry MODE SELECT on command lock violation

2016-01-22 Thread Hannes Reinecke
If MODE SELECT returns with sense '05/91/36' (command lock violation) it should always be retried without counting the number of retries. During an HBA upgrade or similar circumstances one might see a flood of MODE SELECT command from various HBAs, which will easily trigger the sense code and excee