[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-31.50

---
linux (4.4.0-31.50) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1602449

  * nouveau: boot hangs at blank screen with unsupported graphics cards
(LP: #1602340)
- SAUCE: drm: check for supported chipset before booting fbdev off the hw

linux (4.4.0-30.49) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597897

  * FCP devices are not detected correctly nor deterministically (LP: #1567602)
- scsi_dh_alua: Disable ALUA handling for non-disk devices
- scsi_dh_alua: Use vpd_pg83 information
- scsi_dh_alua: improved logging
- scsi_dh_alua: sanitze sense code handling
- scsi_dh_alua: use standard logging functions
- scsi_dh_alua: return standard SCSI return codes in submit_rtpg
- scsi_dh_alua: fixup description of stpg_endio()
- scsi_dh_alua: use flag for RTPG extended header
- scsi_dh_alua: use unaligned access macros
- scsi_dh_alua: rework alua_check_tpgs() to return the tpgs mode
- scsi_dh_alua: simplify sense code handling
- scsi: Add scsi_vpd_lun_id()
- scsi: Add scsi_vpd_tpg_id()
- scsi_dh_alua: use scsi_vpd_tpg_id()
- scsi_dh_alua: Remove stale variables
- scsi_dh_alua: Pass buffer as function argument
- scsi_dh_alua: separate out alua_stpg()
- scsi_dh_alua: Make stpg synchronous
- scsi_dh_alua: call alua_rtpg() if stpg fails
- scsi_dh_alua: switch to scsi_execute_req_flags()
- scsi_dh_alua: allocate RTPG buffer separately
- scsi_dh_alua: Use separate alua_port_group structure
- scsi_dh_alua: use unique device id
- scsi_dh_alua: simplify alua_initialize()
- revert commit a8e5a2d593cb ("[SCSI] scsi_dh_alua: ALUA handler attach 
should
  succeed while TPG is transitioning")
- scsi_dh_alua: move optimize_stpg evaluation
- scsi_dh_alua: remove 'rel_port' from alua_dh_data structure
- scsi_dh_alua: Use workqueue for RTPG
- scsi_dh_alua: Allow workqueue to run synchronously
- scsi_dh_alua: Add new blacklist flag 'BLIST_SYNC_ALUA'
- scsi_dh_alua: Recheck state on unit attention
- scsi_dh_alua: update all port states
- scsi_dh_alua: Send TEST UNIT READY to poll for transitioning
- scsi_dh_alua: do not fail for unknown VPD identification

linux (4.4.0-29.48) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597015

  * Wireless hotkey fails on Dell XPS 15 9550 (LP: #1589886)
- intel-hid: new hid event driver for hotkeys
- intel-hid: fix incorrect entries in intel_hid_keymap
- intel-hid: allocate correct amount of memory for private struct
- intel-hid: add a workaround to ignore an event after waking up from S4.
- [Config] CONFIG_INTEL_HID_EVENT=m

  * cgroupfs mounts can hang (LP: #1588056)
- Revert "UBUNTU: SAUCE: (namespace) mqueue: Super blocks must be owned by 
the
  user ns which owns the ipc ns"
- Revert "UBUNTU: SAUCE: kernfs: Do not match superblock in another user
  namespace when mounting"
- Revert "UBUNTU: SAUCE: cgroup: Use a new super block when mounting in a
  cgroup namespace"
- (namespace) bpf: Use mount_nodev not mount_ns to mount the bpf filesystem
- (namespace) bpf, inode: disallow userns mounts
- (namespace) ipc: Initialize ipc_namespace->user_ns early.
- (namespace) vfs: Pass data, ns, and ns->userns to mount_ns
- SAUCE: (namespace) Sync with upstream s_user_ns patches
- (namespace) kernfs: The cgroup filesystem also benefits from SB_I_NOEXEC
- (namespace) ipc/mqueue: The mqueue filesystem should never contain
  executables

  * KVM system crashes after starting guest (LP: #1596635)
- xhci: Cleanup only when releasing primary hcd

  * Upstream patch "crypto: vmx - IV size failing on skcipher API" for Ubuntu
16.04 (LP: #1596557)
- crypto: vmx - IV size failing on skcipher API

  * [Bug]tpm initialization fails on x86 (LP: #1596469)
- tpm_crb: drop struct resource res from struct crb_priv
- tpm_crb: fix mapping of the buffers

  * Device shutdown notification for CAPI Flash cards (LP: #1592114)
- cxlflash: Fix regression issue with re-ordering patch
- cxlflash: Fix to drain operations from previous reset
- cxlflash: Add device dependent flags
- cxlflash: Shutdown notify support for CXL Flash cards

  * scsi-modules udeb should include pm80xx (LP: #1595628)
- [Config] Add pm80xx scsi driver to d-i

  * Sync up latest relevant upstream bug fixes (LP: #1594871)
- SAUCE: (noup) Update zfs to 0.6.5.6-0ubuntu10

  * Cannot compile module tda10071 (LP: #1592531)
- [media] tda10071: Fix dependency to REGMAP_I2C

  * lsvpd doesn't show correct location code for devices attached to a CAPI card
(LP: #1594847)
- cxl: Make vPHB device node match adapter's

  * enable CRC32 and AES ARM64 by default or as module (LP: #1594455)
- [Config] Enable arm64 AES and CRC32 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.4.0-31.50

---
linux (4.4.0-31.50) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1602449

  * nouveau: boot hangs at blank screen with unsupported graphics cards
(LP: #1602340)
- SAUCE: drm: check for supported chipset before booting fbdev off the hw

linux (4.4.0-30.49) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597897

  * FCP devices are not detected correctly nor deterministically (LP: #1567602)
- scsi_dh_alua: Disable ALUA handling for non-disk devices
- scsi_dh_alua: Use vpd_pg83 information
- scsi_dh_alua: improved logging
- scsi_dh_alua: sanitze sense code handling
- scsi_dh_alua: use standard logging functions
- scsi_dh_alua: return standard SCSI return codes in submit_rtpg
- scsi_dh_alua: fixup description of stpg_endio()
- scsi_dh_alua: use flag for RTPG extended header
- scsi_dh_alua: use unaligned access macros
- scsi_dh_alua: rework alua_check_tpgs() to return the tpgs mode
- scsi_dh_alua: simplify sense code handling
- scsi: Add scsi_vpd_lun_id()
- scsi: Add scsi_vpd_tpg_id()
- scsi_dh_alua: use scsi_vpd_tpg_id()
- scsi_dh_alua: Remove stale variables
- scsi_dh_alua: Pass buffer as function argument
- scsi_dh_alua: separate out alua_stpg()
- scsi_dh_alua: Make stpg synchronous
- scsi_dh_alua: call alua_rtpg() if stpg fails
- scsi_dh_alua: switch to scsi_execute_req_flags()
- scsi_dh_alua: allocate RTPG buffer separately
- scsi_dh_alua: Use separate alua_port_group structure
- scsi_dh_alua: use unique device id
- scsi_dh_alua: simplify alua_initialize()
- revert commit a8e5a2d593cb ("[SCSI] scsi_dh_alua: ALUA handler attach 
should
  succeed while TPG is transitioning")
- scsi_dh_alua: move optimize_stpg evaluation
- scsi_dh_alua: remove 'rel_port' from alua_dh_data structure
- scsi_dh_alua: Use workqueue for RTPG
- scsi_dh_alua: Allow workqueue to run synchronously
- scsi_dh_alua: Add new blacklist flag 'BLIST_SYNC_ALUA'
- scsi_dh_alua: Recheck state on unit attention
- scsi_dh_alua: update all port states
- scsi_dh_alua: Send TEST UNIT READY to poll for transitioning
- scsi_dh_alua: do not fail for unknown VPD identification

linux (4.4.0-29.48) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
- LP: #1597015

  * Wireless hotkey fails on Dell XPS 15 9550 (LP: #1589886)
- intel-hid: new hid event driver for hotkeys
- intel-hid: fix incorrect entries in intel_hid_keymap
- intel-hid: allocate correct amount of memory for private struct
- intel-hid: add a workaround to ignore an event after waking up from S4.
- [Config] CONFIG_INTEL_HID_EVENT=m

  * cgroupfs mounts can hang (LP: #1588056)
- Revert "UBUNTU: SAUCE: (namespace) mqueue: Super blocks must be owned by 
the
  user ns which owns the ipc ns"
- Revert "UBUNTU: SAUCE: kernfs: Do not match superblock in another user
  namespace when mounting"
- Revert "UBUNTU: SAUCE: cgroup: Use a new super block when mounting in a
  cgroup namespace"
- (namespace) bpf: Use mount_nodev not mount_ns to mount the bpf filesystem
- (namespace) bpf, inode: disallow userns mounts
- (namespace) ipc: Initialize ipc_namespace->user_ns early.
- (namespace) vfs: Pass data, ns, and ns->userns to mount_ns
- SAUCE: (namespace) Sync with upstream s_user_ns patches
- (namespace) kernfs: The cgroup filesystem also benefits from SB_I_NOEXEC
- (namespace) ipc/mqueue: The mqueue filesystem should never contain
  executables

  * KVM system crashes after starting guest (LP: #1596635)
- xhci: Cleanup only when releasing primary hcd

  * Upstream patch "crypto: vmx - IV size failing on skcipher API" for Ubuntu
16.04 (LP: #1596557)
- crypto: vmx - IV size failing on skcipher API

  * [Bug]tpm initialization fails on x86 (LP: #1596469)
- tpm_crb: drop struct resource res from struct crb_priv
- tpm_crb: fix mapping of the buffers

  * Device shutdown notification for CAPI Flash cards (LP: #1592114)
- cxlflash: Fix regression issue with re-ordering patch
- cxlflash: Fix to drain operations from previous reset
- cxlflash: Add device dependent flags
- cxlflash: Shutdown notify support for CXL Flash cards

  * scsi-modules udeb should include pm80xx (LP: #1595628)
- [Config] Add pm80xx scsi driver to d-i

  * Sync up latest relevant upstream bug fixes (LP: #1594871)
- SAUCE: (noup) Update zfs to 0.6.5.6-0ubuntu10

  * Cannot compile module tda10071 (LP: #1592531)
- [media] tda10071: Fix dependency to REGMAP_I2C

  * lsvpd doesn't show correct location code for devices attached to a CAPI card
(LP: #1594847)
- cxl: Make vPHB device node match adapter's

  * enable CRC32 and AES ARM64 by default or as module (LP: #1594455)
- [Config] Enable arm64 AES and CRC32 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Stefan Bader]

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Kamal Mostafa]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Kamal Mostafa]

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Stefan Bader]

Added a new attempt. This time the pick-list is rather excessive.
Unfortunately the more likely changes come later. So while there might
be some patches which probably can be dropped, I fear the overall set
still will be big. (Download again:
http://people.canonical.com/~smb/lp1567602/)

5da8bf5 scsi_dh_alua: Disable ALUA handling for non-disk devices
71b066c scsi_dh_alua: Use vpd_pg83 information
fc63978 scsi_dh_alua: improved logging
5e60928 scsi_dh_alua: sanitze sense code handling
73a86b1 scsi_dh_alua: use standard logging functions
9ba4fe6 scsi_dh_alua: return standard SCSI return codes in submit_rtpg
ae5408e scsi_dh_alua: fixup description of stpg_endio()
79ded51 scsi_dh_alua: use flag for RTPG extended header
9121b4c scsi_dh_alua: use unaligned access macros
ce6f796 scsi_dh_alua: rework alua_check_tpgs() to return the tpgs mode
567d885 scsi_dh_alua: simplify sense code handling
c6fe649 scsi: Add scsi_vpd_lun_id()
f52649f scsi: Add scsi_vpd_tpg_id()
cdacdc7 scsi_dh_alua: use scsi_vpd_tpg_id()
6a49629 scsi_dh_alua: Remove stale variables
fdd3a8c scsi_dh_alua: Pass buffer as function argument
542a8c0 scsi_dh_alua: separate out alua_stpg()
ab7ae03 scsi_dh_alua: Make stpg synchronous
fe551f5 scsi_dh_alua: call alua_rtpg() if stpg fails
fc55215 scsi_dh_alua: switch to scsi_execute_req_flags()
0b98a60 scsi_dh_alua: allocate RTPG buffer separately
e4dee21 scsi_dh_alua: Use separate alua_port_group structure
ecec8731 scsi_dh_alua: use unique device id
b20a55f scsi_dh_alua: simplify alua_initialize()
81537d5 revert commit a8e5a2d593cb ("[SCSI] scsi_dh_alua: ALUA handler attach sh
487cdf2 scsi_dh_alua: move optimize_stpg evaluation
b5cbbc6 scsi_dh_alua: remove 'rel_port' from alua_dh_data structure
dd2af31 scsi_dh_alua: Use workqueue for RTPG
bdf2fc3 scsi_dh_alua: Allow workqueue to run synchronously
a936713 scsi_dh_alua: Add new blacklist flag 'BLIST_SYNC_ALUA'
d69dd4d scsi_dh_alua: Recheck state on unit attention
abcf58c scsi_dh_alua: update all port states
82d5f45 scsi_dh_alua: Send TEST UNIT READY to poll for transitioning
676fa7c scsi_dh_alua: Update version to 2.0
9f33778 scsi_dh_alua: do not fail for unknown VPD identification

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Stefan Bader]

Thanks Thorsten. So I have to go back and see what else might be
relevant. Just for reference the one patch I used (forgot to mention
this earlier) was the one below:

Author: Hannes Reinecke 
Date:   Tue Dec 1 10:16:44 2015 +0100

scsi_dh_alua: Use vpd_pg83 information

The SCSI device now has the VPD page 0x83 information attached,
so there is no need to query it again.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Stefan Bader]

Or better it should be 4.6+ at some point. I realized it still is a copy
of Xenial (4.4). But I would not worry about the fix there.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Stefan Bader]

Set main task back to fix released as that is then devel release which
is 4.6+ and that is claimed to work.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Mathew Hodson]

** Changed in: linux (Ubuntu)
   Status: Fix Released => Confirmed

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  In Progress

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[kaniggl]

sorry, cliecked something wrong. Please delete my changes.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  In Progress

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: INFO: Menu 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Stefan Bader]

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Stefan Bader (smb)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  In Progress

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Stefan Bader]

Hi Thorsten, so maybe (if the main issue is the inquiry) it is possible
to get away with just picking the change that appears to remove that in
favour of present device information. Could you try the kernel at
http://people.canonical.com/~smb/lp1567602/ in your environment and let
me know whether that helps anything?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-zfcp' selected
  Apr  6 12:57:10 s390-zfcp[6891]: DEBUG: 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Dimitri John Ledkov]

@ Thorsten

We should be working together, because we do not have the mainframe
setup/config which reproduces / exhibits this bug. And possibly neither
upstream maintainer. It is common code, but the bug is triggered on
hardware config and platform that IBM ships.

** Changed in: linux (Ubuntu)
 Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel 
(canonical-kernel)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Dimitri John Ledkov]

@Thorsten

A large affected userbase is important to us. What I was trying to point
out is that even without any added work done (e.g. figuring out where
the fix is, and backporting it to v4.4 series) this will be resolved in
the 14.04 series via hwe kernel.

At this point, this appears to be a linux upstream issue. Could you
please escalate this issue to the IBM kernel team? I would assume it
would be in your interest to cherrypick/backport fixes for this issue
into the v4.4-stable tree, which would then be picked up by us for 16.04
- v4.4 kernel.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Triaged => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-zfcp' selected
  Apr  6 12:57:10 s390-zfcp[6891]: 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Dimitri John Ledkov]

@ Benjamin

Thank you for your insights. Is it possible to determine a scope of
affected systems out there? So far a specific config is required to
trigger this bug it seems, but I'm not sure how common such a
configuration is. Extensive back-ports and reworks of the kernel are out
of the question. However, we do have LTS hardware enablement kernel
stacks -
https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Kernel.2FSupport.A16.04.x_Ubuntu_Kernel_Support
in essence, some time after 16.10 release, the 16.10 kernels will be
backported to 16.04, and 16.04.2 release installation media will use the
updated kernel by default - v4.8 (current estimate for 16.10 kernel),
such that affected systems will be able to use much newer kernel during
installation and regular runtime eventually in the future (current
approximate timing February 2017).

Is it at all possible to test this issue with mainline kernels? and/or I
guess we can wait for 16.10 to get upgraded kernel and retest on 16.10
to see if this issue is resolved with a newer kernel.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-zfcp' selected
  Apr  6 12:57:10 s390-zfcp[6891]: DEBUG: 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Dimitri John Ledkov]

** Changed in: linux (Ubuntu)
   Importance: High => Undecided

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-zfcp' selected
  Apr  6 12:57:10 s390-zfcp[6891]: DEBUG: DETECT: The 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Mathew Hodson]

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-zfcp' selected
  Apr  6 12:57:10 s390-zfcp[6891]: DEBUG: DETECT: The 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Dimitri John Ledkov]

** Changed in: ubuntu-release-notes
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Release notes:
  Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.


  
  Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
    Vendor: IBM  Model: 2107900  Rev: 1.27
    Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-zfcp' selected
  Apr  6 12:57:10 s390-zfcp[6891]: DEBUG: 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Dimitri John Ledkov]

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

** Description changed:

- Scenario: 
+ Release notes:
+ Usage of SCSI LUNs on DS8870 Storage server with μCode Bundles 87.51.xx.0 
(LMC 7.7.51.xx) via NPIV enabled zfcp adaptors causes detection issues. LP 
#1567602 In that case do not use NPIV enabled zfcp adaptors.
+ 
+ 
+ 
+ Scenario:
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.
  
  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.
  
  Subsequent steps to create partitions and file systems in the installer
  fail.
  
  Following is one of the five cases with more details:
  After enabling CHPID 192b:
- ~ # cat /proc/scsi/scsi 
+ ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
-   Vendor: IBM  Model: 2107900  Rev: 1.27
-   Type:   Direct-AccessANSI  SCSI revision: 05
+   Vendor: IBM  Model: 2107900  Rev: 1.27
+   Type:   Direct-AccessANSI  SCSI revision: 05
  
  dmesg showing:
- [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
+ [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted
  
  As second step, I additionally enable CHPID 196b:
- ~ # cat /proc/scsi/scsi 
+ ~ # cat /proc/scsi/scsi
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
-   Vendor: IBM  Model: 2107900  Rev: 1.27
-   Type:   Direct-AccessANSI  SCSI revision: 05
+   Vendor: IBM  Model: 2107900  Rev: 1.27
+   Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
-   Vendor: IBM  Model: 2107900  Rev: 1.27
-   Type:   Direct-AccessANSI  SCSI revision: 05
+   Vendor: IBM  Model: 2107900  Rev: 1.27
+   Type:   Direct-AccessANSI  SCSI revision: 05
  
  dmesg showing:
  [  384.277394] scsi host1: zfcp
- [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
+ [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted
  
  Next, the installer warns that no disk drives were detected.
  
  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:
  
  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Dimitri John Ledkov]

** No longer affects: ubuntu-release-notes

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Scenario: 
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi 
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi 
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-zfcp' selected
  Apr  6 12:57:10 s390-zfcp[6891]: DEBUG: DETECT: The zfcp device driver is not 
loaded
  Apr  6 12:57:10 s390-zfcp[6891]: WARNING **: Could not open directory: 
/sys/bus/ccw/drivers/zfcp/: No such file or directory
  Apr  6 12:57:11 main-menu[384]: INFO: Menu item 'disk-detect' selected
  Apr  6 12:57:11 anna-install: Installing mmc-modules
  Apr  6 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Stefan Bader]

Sorry no, what I meant was that I do not see any problem. All LUNs get
detected, no error message about alua.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  New
Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Scenario: 
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi 
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi 
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-zfcp' selected
  Apr  6 12:57:10 s390-zfcp[6891]: DEBUG: DETECT: The zfcp device driver is not 
loaded
  Apr  6 12:57:10 s390-zfcp[6891]: WARNING **: Could not open directory: 
/sys/bus/ccw/drivers/zfcp/: No such file or directory
  Apr  6 12:57:11 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[ChristianEhrhardt]

FYI - Storage Server is on older version 5.7.41.1028

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  New
Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Scenario: 
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi 
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi 
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-zfcp' selected
  Apr  6 12:57:10 s390-zfcp[6891]: DEBUG: DETECT: The zfcp device driver is not 
loaded
  Apr  6 12:57:10 s390-zfcp[6891]: WARNING **: Could not open directory: 
/sys/bus/ccw/drivers/zfcp/: No such file or directory
  Apr  6 12:57:11 main-menu[384]: INFO: Menu item 'disk-detect' selected
  Apr  6 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[ChristianEhrhardt]

Just to be sure I did a cross check on my lpar:

Cleaning my system to get an empty condition at the start
sudo chzdev zfcp-lun --all --disable --force
sudo chzdev zfcp-host --all --disable --force
sudo chzdev zfcp --all --disable --force

Now it looks like the one from Thorsten:

ubuntu@s1lp5:~$ lscss |grep 1732/03
0.0.e000 0.0.0d4d  1732/03 1731/03  80  80  ff   2000  
0.0.e001 0.0.0d4e  1732/03 1731/03  80  80  ff   2000  
0.0.e002 0.0.0d4f  1732/03 1731/03  80  80  ff   2000  
0.0.e003 0.0.0d50  1732/03 1731/03  80  80  ff   2000  
0.0.e004 0.0.0d51  1732/03 1731/03  80  80  ff   2000  
0.0.e005 0.0.0d52  1732/03 1731/03  80  80  ff   2000  
0.0.e006 0.0.0d53  1732/03 1731/03  80  80  ff   2000  
0.0.e007 0.0.0d54  1732/03 1731/03  80  80  ff   2000  
0.0.e008 0.0.0d55  1732/03 1731/03  80  80  ff   2000  
0.0.e009 0.0.0d56  1732/03 1731/03  80  80  ff   2000  
0.0.e00a 0.0.0d57  1732/03 1731/03  80  80  ff   2000  
0.0.e00b 0.0.0d58  1732/03 1731/03  80  80  ff   2000  
0.0.e00c 0.0.0d59  1732/03 1731/03  80  80  ff   2000  
0.0.e00d 0.0.0d5a  1732/03 1731/03  80  80  ff   2000  
0.0.e00e 0.0.0d5b  1732/03 1731/03  80  80  ff   2000  
0.0.e00f 0.0.0d5c  1732/03 1731/03  80  80  ff   2000  
0.0.e100 0.0.0d5d  1732/03 1731/03  80  80  ff   2100  
0.0.e101 0.0.0d5e  1732/03 1731/03  80  80  ff   2100  
0.0.e102 0.0.0d5f  1732/03 1731/03  80  80  ff   2100  
0.0.e103 0.0.0d60  1732/03 1731/03  80  80  ff   2100  
0.0.e104 0.0.0d61  1732/03 1731/03  80  80  ff   2100  
0.0.e105 0.0.0d62  1732/03 1731/03  80  80  ff   2100  
0.0.e106 0.0.0d63  1732/03 1731/03  80  80  ff   2100  
0.0.e107 0.0.0d64  1732/03 1731/03  80  80  ff   2100  
0.0.e108 0.0.0d65  1732/03 1731/03  80  80  ff   2100  
0.0.e109 0.0.0d66  1732/03 1731/03  80  80  ff   2100  
0.0.e10a 0.0.0d67  1732/03 1731/03  80  80  ff   2100  
0.0.e10b 0.0.0d68  1732/03 1731/03  80  80  ff   2100  
0.0.e10c 0.0.0d69  1732/03 1731/03  80  80  ff   2100  
0.0.e10d 0.0.0d6a  1732/03 1731/03  80  80  ff   2100  
0.0.e10e 0.0.0d6b  1732/03 1731/03  80  80  ff   2100  
0.0.e10f 0.0.0d6c  1732/03 1731/03  80  80  ff   2100  
ubuntu@s1lp5:~$ lsluns -a
ubuntu@s1lp5:~$ lsmod |grep scsi_dh


Then following Thorstens guide to trigger on live system
1. the one without alua being ok:
ubuntu@s1lp5:~$ sudo chccwdev -e 0.0.e000
Setting device 0.0.e000 online
Done
ubuntu@s1lp5:~$ lszfcp -D
0.0.e000/0x50050763061b16b6/0x40244002 1:0:0:1073889316
0.0.e000/0x50050763061b16b6/0x40244003 1:0:0:1073954852
0.0.e000/0x50050763060b16b6/0x40244002 1:0:1:1073889316
0.0.e000/0x50050763060b16b6/0x40244003 1:0:1:1073954852

2. the one after loading alua with issues:
ubuntu@s1lp5:~$ sudo modprobe scsi_dh_alua
ubuntu@s1lp5:~$ lsmod |grep scsi_dh
scsi_dh_alua   20480  0
ubuntu@s1lp5:~$ sudo chccwdev -e e100
Setting device 0.0.e100 online
Done
ubuntu@s1lp5:~$ lszfcp -D
0.0.e000/0x50050763061b16b6/0x40244002 1:0:0:1073889316
0.0.e000/0x50050763061b16b6/0x40244003 1:0:0:1073954852
0.0.e000/0x50050763060b16b6/0x40244002 1:0:1:1073889316
0.0.e000/0x50050763060b16b6/0x40244003 1:0:1:1073954852
0.0.e100/0x50050763061b16b6/0x40244002 0:0:0:1073889316
0.0.e100/0x50050763061b16b6/0x40244003 0:0:0:1073954852
0.0.e100/0x50050763060b16b6/0x40244002 0:0:1:1073889316
0.0.e100/0x50050763060b16b6/0x40244003 0:0:1:1073954852


dmesg also good with alua on for the second adapter being enabled => 
http://paste.ubuntu.com/15951140/

So I can confirm Stefans summary.

Thorsten please try to reproduce on a fully updated system, if not
resolved for you we have to start to sort out the remaining differences
in our environment.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  New
Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Scenario: 
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Stefan Bader]

I also tried to re-create this on one of the lpars we got. No luck
either. However I was using the latest kernel which was uploaded just
... I think yesterday (4.4.0-21). Thorsten, maybe you can try that
version, too. Just to be on the safe side.

The dmesg I get also shows that alua probing is done. So that sounds to
be going through the exactly same sequence. We got NPIV enabled, too.
Only here I also got dasd which we use to ipl from. Mainly speculating
here but it feels a bit like maybe newer kernels might send out inquiry
commands quicker or in parallel and something in the environment fails
to cope with that and silently drops some requests...

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  New
Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Scenario: 
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi 
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi 
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Dimitri John Ledkov]

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Release Notes for Ubuntu:
  New
Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Scenario: 
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi 
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi 
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-zfcp' selected
  Apr  6 12:57:10 s390-zfcp[6891]: DEBUG: DETECT: The zfcp device driver is not 
loaded
  Apr  6 12:57:10 s390-zfcp[6891]: WARNING **: Could not open directory: 
/sys/bus/ccw/drivers/zfcp/: No such file or directory
  Apr  6 12:57:11 main-menu[384]: INFO: Menu item 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[bugproxy]

** Tags removed: targetmilestone-inin1604
** Tags added: targetmilestone-inin16041

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Scenario: 
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi 
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi 
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-zfcp' selected
  Apr  6 12:57:10 s390-zfcp[6891]: DEBUG: DETECT: The zfcp device driver is not 
loaded
  Apr  6 12:57:10 s390-zfcp[6891]: WARNING **: Could not open directory: 
/sys/bus/ccw/drivers/zfcp/: No such file or directory
  Apr  6 12:57:11 main-menu[384]: INFO: Menu item 'disk-detect' selected
  Apr  6 12:57:11 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Dimitri John Ledkov]

Also w.r.t. multipath, disk-detect/multipath/enable is now enabled by
default on Ubuntu on s390x, thus multipath installer codepath should be
the one offered by the installer when the devices are scanned correctly.
Moving this bug report to kernel package, as it seems to me this is a
kernel issue and it's not the installer logic that is at fault.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Scenario: 
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi 
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi 
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-zfcp' selected
  Apr  6 12:57:10 s390-zfcp[6891]: DEBUG: DETECT: 

[Kernel-packages] [Bug 1567602] Re: FCP devices are not detected correctly nor deterministically

[Dimitri John Ledkov]

So this is an upstream kernel regression with certain hardware
configuration? I'm looking into scans as seen on our hardware, but it
appears to be consistently discovered on our combinations of hardware,
but will stress test that more.

** Package changed: debian-installer (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1567602

Title:
  FCP devices are not detected correctly nor deterministically

Status in Ubuntu on IBM z Systems:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Scenario: 
  Using Installer 432.
  No DASD devices, just two FCP CHPIDs with two LUNs each (configured for 
NPIV), provided via parmfile.
  I expect the installer to probe and detect the LUNs automatically once I 
enable the FCP CHPIDs.

  Repeated five times, I got different results each time. Detected LUNs
  vary between 2 and 4. One time 3 LUNs appear on SCSI1 and one on SCSI2
  which looks especially odd to me.

  Subsequent steps to create partitions and file systems in the
  installer fail.

  Following is one of the five cases with more details:
  After enabling CHPID 192b:
  ~ # cat /proc/scsi/scsi 
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  221.738816] qdio: 0.0.192b ZFCP on SC f using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
  [  226.895139] scsi 0:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  226.895816] sd 0:0:0:1077493890: alua: supports implicit TPGS
  [  226.896673] sd 0:0:0:1077493890: [sda] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  226.897825] sd 0:0:0:1077493890: [sda] Write Protect is off
  [  226.897827] sd 0:0:0:1077493890: [sda] Mode Sense: ed 00 00 08
  [  226.898145] sd 0:0:0:1077493890: [sda] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  226.902571] sd 0:0:0:1077493890: [sda] Attached SCSI disk
  [  287.117057] sd 0:0:0:1077493890: alua: evpd inquiry failed with 3
  [  287.117062] sd 0:0:0:1077493890: alua: Attach failed (-22)
  [  287.117064] sd 0:0:0:1077493890: failed to add device handler: -22
  [  287.147303] scsi 0:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  As second step, I additionally enable CHPID 196b:
  ~ # cat /proc/scsi/scsi 
  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 1077493890
Vendor: IBM  Model: 2107900  Rev: 1.27
Type:   Direct-AccessANSI  SCSI revision: 05

  dmesg showing:
  [  384.277394] scsi host1: zfcp
  [  384.286516] qdio: 0.0.196b ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1 TDD:1 
SIGA: W A 
  [  385.377511] scsi 1:0:0:1077493890: Direct-Access IBM  2107900  
1.27 PQ: 0 ANSI: 5
  [  385.378120] sd 1:0:0:1077493890: alua: supports implicit TPGS
  [  385.378781] sd 1:0:0:1077493890: [sdb] 41943040 512-byte logical blocks: 
(21.5 GB/20.0 GiB)
  [  385.380097] sd 1:0:0:1077493890: [sdb] Write Protect is off
  [  385.380099] sd 1:0:0:1077493890: [sdb] Mode Sense: ed 00 00 08
  [  385.380408] sd 1:0:0:1077493890: [sdb] Write cache: enabled, read cache: 
enabled, doesn't support DPO or FUA
  [  385.384969] sd 1:0:0:1077493890: [sdb] Attached SCSI disk
  [  446.117041] sd 1:0:0:1077493890: alua: evpd inquiry failed with 3
  [  446.117046] sd 1:0:0:1077493890: alua: Attach failed (-22)
  [  446.117048] sd 1:0:0:1077493890: failed to add device handler: -22
  [  446.147158] scsi 1:0:0:0: Unexpected response from lun 1077493890 while 
scanning, scan aborted

  Next, the installer warns that no disk drives were detected.

  I checked this on a system (installer 445) with two NPIV enabled FCP
  devices that have 4 LUNS each. I only get the first of four LUNs per
  adaptor:

  Apr  6 12:57:08 anna[2607]: DEBUG: retrieving zipl-installer 0.0.33ubuntu2
  Apr  6 12:57:08 anna[2607]: 2016-04-06 12:57:08 
URL:http://ports.ubuntu.com//pool/main/z/zipl-installer/zipl-installer_0.0.33ubuntu2_s390x.udeb
 [4994/4994] -> "/var/cache/anna/zipl-installer_0.0.33ubuntu2_s390x.udeb" [1]
  Apr  6 12:57:09 main-menu[384]: INFO: Menu item 
'driver-injection-disk-detect' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'user-setup-udeb' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 'clock-setup' selected
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-dasd' selected
  Apr  6 12:57:10 s390-dasd[6877]: INFO: s390-dasd: no channel found
  Apr  6 12:57:10 main-menu[384]: INFO: Menu item 's390-zfcp' selected
  Apr  6 12:57:10 s390-zfcp[6891]: DEBUG: DETECT: The zfcp device driver is not 
loaded
  Apr  6