On 03/07/2014 12:43 AM, Jeremy Linton wrote:
> On 1/31/2014 3:29 AM, Hannes Reinecke wrote:
>> Improve error handling and use standard logging functions
>> instead of hand-crafted ones.
>>
>> @@ -182,11 +185,13 @@ static unsigned submit_rtpg(struct scsi_device *sdev, struct alua_dh_data *h,
>> bool rtpg_ext_hdr_req)
>
> Can you shorten the timeouts for this?
>
> I think submit_rtpg failures are causing a boot failure on a SLES 11 SP2
> machine (3.0.101-0.7.17-default). The basic configuration is an ACNC jetstor,
> mapped as a raw LUN through a vmware (esxi 5.5) virtual mptsas adapter. The sd
> driver seems to be jamming up udev's creation of the boot /dev entries with a
> ~360 second delay probing /dev/sdb. This causes the /dev/sda entry for the root
> partition (on another device) not to show up in time.
>
>
> (output from a screen capture sent to me/ocr'ed)
>
> [ 2.918164] sdev dma_alignment 511
> [ 3.917810] mptsas2 ioc02 attaching ssp device2 fw_channel 0, fu_id 1, phg 1,
> sas_addr 0x5000
> c29f6c78b0af
> [ 3.920204] scsi target0:0:1: mptsas2: ioc02: add device: fw_channel 0, fw_id 1,
> phy 1, sas_add
> r 0x5000c29f6c78b0af
> [ 3.921923] scsi 02021202 Direct-Access JetStor VMB-00 R001 PQ: 0 ANSI: 5
> [ 4.824734] scsi 02021202 mptscsih: ioc0: qdepth=64, tagged=1, simple=1,
> ordered:0, scsi_level:6, cmd_que=1
> [ 4.827184] sdev dma_alignment 511
> [ 4.828006] scsi 02021202 alua: supports implicit TPGS
> [ 4.828897] scsi 02021202 alua: target naa.2000001B4D01CA59 port group 01 rel
> port 1b
> [ 4.830084] scsi 02021202 alua: Attached
> [ 4.834297] sd 0:0:0:0: [sda] 33554432 512-byte logical blocks: (17.1 GB/16.0 GiB)
> [ 4.835141] sd 02020202 [sda] Write Protect is off
> [ 4.835954] sd 02020202 [sda] Mode Sense2 61 00 00 00
> [ 4.835994] sd 02020202 [sda] Cache data unavailable
> [ 4.836808] sd 02020202 [sda] Assuming drive cache2 write through
> [ 4.837718] sd 0:0:1:02 [sdb] 390623744 512-byte logical blocks: (199 GB/186 GiB)
> [ 4.837756] sd 02020202 [sda] Cache data unavailable
> [ 4.837758] sd 02020202 [sda] Assuming drive cache2 write through
> [ 4.870098] sda2 sdal sda2
> [ 4.871675] sd 02020202 [sda] Cache data unavailable
> [ 4.872461] sd 02020202 [sda] Assuming drive cache2 write through
> [ 4.873243] sd 02020202 [sda] Attached SCSI disk
> [ 5.622838] sd 02021202 [sdb] Write Protect is off
> [ 5.624410] sd 02021202 [sdb] Mode Sense2 bf 00 00 08
> [ 5.624654] sd 02021202 [sdb] Write cache2 enabled, read cache2 enabled, doesn’t
> support DPO or FUA
> [ 364.290276] sd 02021202 timing out command, waited 360s
> [ 364.291495] sd 02021202 alua2 rtpg failed, Result2 hostbgte=DID_OK
> driuerbgte:DRIVER_OK
> [ 364.309198] sdb: sdbl
> [ 367.890274] sd 02021202 [sdb] Attached SCSI disk
>
>
> vmware says this about the disk:
>
> naa.6001b4d4373468630000000000000000
> Device Display Name: JetStor Fibre Channel Disk (naa.6001b4d43734686300000000
> 00000000)
> Storage Array Type: VMW_SATP_ALUA
> Storage Array Type Device Config: {implicit_support=on;explicit_support=off;
>
> explicit_allow=on;alua_followover=on;{TPG_id=1,TPG_state=ANO}}
> Path Selection Policy: VMW_PSP_MRU
> Path Selection Policy Device Config: Current Path=vmhba5:C0:T0:L1
> Path Selection Policy Device Custom Config:
> Working Paths: vmhba5:C0:T0:L1
> Is Local SAS Device: false
> Is Boot USB Device: false
>
>
Hehe. Infamous 'timing out command' message.
That smells more like a weird interaction going on there.
Can you file a bug with bugzilla.novell.com and assign it to me?
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@xxxxxxx +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
