https://bugzilla.novell.com/show_bug.cgi?id=867371 https://bugzilla.novell.com/show_bug.cgi?id=867371#c0 Summary: SLES 11 SP2 boot failure with ALUA timeouts on vmware with raw FC attached disk Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: jlinton@tributary.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.146 Safari/537.36 Using a SLES 11 SP2 kernel 3.0.101-0.7.17-default, the virtual machine fails to boot when a raw device is passed through the virtual mptsas adapter. In this case the raw device is a ACNC FC attached Jetstor (attached via an emulex FC adapter). The sda/root device (which is just a vmware virtual volume) is accessible if the /dev entries are manually created with mknod, but udev is unable to create them until sd finishes probing the sdb/raw disk device. Here is an OCR'ed screen capture (AKA may contain typos) dmesg output: [ 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/160 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 raw disk device: 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 Reproducible: Always Steps to Reproduce: 1. Install/Upgrade latest SLES 11 SP2 on vmware hypervisor/ESXi 5.5 with virtual mptsas adapter 2. Add a RAW device pass-through to a FC attached ACNC Jetstor 742. 3. Reboot Actual Results: Boot failure due to missing /dev/sd* entries. Expected Results: Systems boots. I can probably open a proper support ticket if that helps anyone, otherwise this is not really a high priority (for us, yet) as its in a testing environment. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.