[Bug 2133480] Comment bridged from LTC Bugzilla

[bugproxy]

------- Comment From aditi.0205 at ibm.com 2026-03-16 13:53 EDT-------
HI fheimes,

In my setup, its case A where each HBA sees every LUNs.
To prove this, below are some commands results:

-----------------------------------------------------------------
In my setup, there are two FC link:

root at ubuntu-server:/# lspci | grep -i fibre
002b:01:00.0 Fibre Channel: QLogic Corp. ISP2812-based 64/32G Fibre Channel to PCIe Controller (rev 02)
002b:01:00.1 Fibre Channel: QLogic Corp. ISP2812-based 64/32G Fibre Channel to PCIe Controller (rev 02)

-----------------------------------------------------------------

root at ubuntu-server:/# ls /sys/class/fc_host
host1  host2  host3

-----------------------------------------------------------------

root at ubuntu-server:/# cat /sys/class/fc_host/host*/port_name
0xffffffffffffffff
0x2100f4c7aa00a2a8
0x2100f4c7aa00a2a9

-----------------------------------------------------------------

root at ubuntu-server:/# for i in /sys/class/scsi_host/host*; do
echo $i
cat $i/proc_name
done
/sys/class/scsi_host/host0
ibmvscsi
/sys/class/scsi_host/host1
ibmvfc
/sys/class/scsi_host/host2
(null)
/sys/class/scsi_host/host3
(null)

----------------------------------------------------------------

root at ubuntu-server:/# readlink -f /sys/class/fc_host/host*/device
/sys/devices/vio/300000ca/host1
/sys/devices/pci002b:01/002b:01:00.0/host2
/sys/devices/pci002b:01/002b:01:00.1/host3

----------------------------------------------------------------

root at ubuntu-server:/# readlink -f /sys/class/scsi_host/host*/device
/sys/devices/vio/30000066/host0
/sys/devices/vio/300000ca/host1
/sys/devices/pci002b:01/002b:01:00.0/host2
/sys/devices/pci002b:01/002b:01:00.1/host3

----------------------------------------------------------------

root at ubuntu-server:/# ls /sys/class/scsi_device
0:0:1:0	 3:0:0:0  3:0:0:2  3:0:0:4  3:0:0:6  3:0:0:8  3:0:1:0  3:0:1:2	3:0:1:4	 3:0:1:6  3:0:1:8
0:0:2:0	 3:0:0:1  3:0:0:3  3:0:0:5  3:0:0:7  3:0:0:9  3:0:1:1  3:0:1:3	3:0:1:5	 3:0:1:7  3:0:1:9

-----------------------------------------------------------------

root at ubuntu-server:/# ls -l /sys/block/sd*/device
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sda/device -> ../../../0:0:1:0
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdb/device -> ../../../3:0:0:0
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdc/device -> ../../../3:0:0:1
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdd/device -> ../../../3:0:0:2
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sde/device -> ../../../3:0:0:3
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdf/device -> ../../../3:0:0:4
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdg/device -> ../../../3:0:0:5
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdh/device -> ../../../3:0:0:6
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdi/device -> ../../../3:0:0:7
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdj/device -> ../../../3:0:0:8
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdk/device -> ../../../3:0:0:9
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdl/device -> ../../../3:0:1:0
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdm/device -> ../../../3:0:1:1
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdn/device -> ../../../3:0:1:2
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdo/device -> ../../../3:0:1:3
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdp/device -> ../../../3:0:1:4
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdq/device -> ../../../3:0:1:5
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdr/device -> ../../../3:0:1:6
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sds/device -> ../../../3:0:1:7
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdt/device -> ../../../3:0:1:8
lrwxrwxrwx 1 root root 0 Mar 16 22:06 /sys/block/sdu/device -> ../../../3:0:1:9

----------------------------------------------------------------------------------

mpatha (360050768108001b3a8000000000001d9) dm-0 IBM,2145
size=50G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 3:0:1:0 sdl 8:176 active ready running
`-+- policy='service-time 0' prio=10 status=enabled
`- 3:0:0:0 sdb 8:16  active ready running
mpathb (360050768108001b3a8000000000001da) dm-1 IBM,2145
size=50G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 3:0:0:1 sdc 8:32  active ready running
`-+- policy='service-time 0' prio=10 status=enabled
`- 3:0:1:1 sdm 8:192 active ready running
mpathc (360050768108001b3a8000000000001db) dm-5 IBM,2145
size=50G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 3:0:1:2 sdn 8:208 active ready running
`-+- policy='service-time 0' prio=10 status=enabled
`- 3:0:0:2 sdd 8:48  active ready running
mpathd (360050768108001b3a8000000000001dc) dm-9 IBM,2145
size=50G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 3:0:0:3 sde 8:64  active ready running
`-+- policy='service-time 0' prio=10 status=enabled
`- 3:0:1:3 sdo 8:224 active ready running
mpathe (360050768108001b3a8000000000001dd) dm-13 IBM,2145
size=50G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 3:0:1:4 sdp 8:240 active ready running
`-+- policy='service-time 0' prio=10 status=enabled
`- 3:0:0:4 sdf 8:80  active ready running
mpathf (360050768108001b3a8000000000001de) dm-17 IBM,2145
size=50G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 3:0:0:5 sdg 8:96 active ready running
`-+- policy='service-time 0' prio=10 status=enabled
`- 3:0:1:5 sdq 65:0 active ready running
mpathg (360050768108001b3a800000000000301) dm-21 IBM,2145
size=50G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 3:0:0:6 sdh 8:112 active ready running
`-+- policy='service-time 0' prio=10 status=enabled
`- 3:0:1:6 sdr 65:16 active ready running
mpathh (360050768108001b3a800000000000302) dm-25 IBM,2145
size=50G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 3:0:1:7 sds 65:32 active ready running
`-+- policy='service-time 0' prio=10 status=enabled
`- 3:0:0:7 sdi 8:128 active ready running
mpathi (360050768108001b3a800000000000303) dm-29 IBM,2145
size=50G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 3:0:0:8 sdj 8:144 active ready running
`-+- policy='service-time 0' prio=10 status=enabled
`- 3:0:1:8 sdt 65:48 active ready running
mpathj (360050768108001b3a800000000000304) dm-33 IBM,2145
size=50G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 3:0:1:9 sdu 65:64 active ready running
`-+- policy='service-time 0' prio=10 status=enabled
`- 3:0:0:9 sdk 8:160 active ready running

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to subiquity in Ubuntu.
https://bugs.launchpad.net/bugs/2133480

Title:
  Ubuntu25.10: Ubuntu host installation is failing while doing
  installation on multiple[2 or more] multipath SAN disks!

Status in The Ubuntu-power-systems project:
  New
Status in subiquity package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Anushree Mathur <Anushree.Mathur2 at ibm.com> - 2025-11-28 03:12:11 ==
  ENV :
  HOST OS : Ubuntu 25.10 

  Host installation is crashing with following crash when we do
  installation on multiple[2 or more] SAN disks and we see -EBUSY error
  with specific mpath disk.

  generating crash report
  report saved to /var/crash/1760429899.735880613.ui.crash
  Traceback (most recent call last):
    File "/snap/subiquity/6868/lib/python3.12/site-packages/subiquity/client/controllers/filesystem.py", line 296, in _guided_choice
      self.ui.set_body(FilesystemView(self.model, self))
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/snap/subiquity/6868/lib/python3.12/site-packages/subiquity/ui/views/filesystem/filesystem.py", line 485, in __init__
      self.refresh_model_inputs()
    File "/snap/subiquity/6868/lib/python3.12/site-packages/subiquity/ui/views/filesystem/filesystem.py", line 544, in refresh_model_inputs
      self.used_list.refresh_model_inputs()
    File "/snap/subiquity/6868/lib/python3.12/site-packages/subiquity/ui/views/filesystem/filesystem.py", line 417, in refresh_model_inputs
      for obj, cells in summarize_device(device, filter):
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/snap/subiquity/6868/lib/python3.12/site-packages/subiquity/ui/views/filesystem/helpers.py", line 32, in summarize_device
      anns = labels.annotations(device) + labels.usage_labels(device)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/snap/subiquity/6868/usr/lib/python3.12/functools.py", line 909, in wrapper
      return dispatch(args[0].__class__)(*args, **kw)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/snap/subiquity/6868/lib/python3.12/site-packages/subiquity/common/filesystem/labels.py", line 101, in _annotations_vg
      member = next(iter(vg.devices))
               ^^^^^^^^^^^^^^^^^^^^^^
  StopIteration

  The above exception was the direct cause of the following exception:

  Traceback (most recent call last):
    File "/snap/subiquity/6868/usr/bin/subiquity", line 8, in <module>
      sys.exit(main())
               ^^^^^^
    File "/snap/subiquity/6868/lib/python3.12/site-packages/subiquity/cmd/tui.py", line 161, in main
      asyncio.run(run_with_loop())
    File "/snap/subiquity/6868/usr/lib/python3.12/asyncio/runners.py", line 194, in run
      return runner.run(main)
             ^^^^^^^^^^^^^^^^
    File "/snap/subiquity/6868/usr/lib/python3.12/asyncio/runners.py", line 118, in run
      return self._loop.run_until_complete(task)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/snap/subiquity/6868/usr/lib/python3.12/asyncio/base_events.py", line 687, in run_until_complete
      return future.result()
             ^^^^^^^^^^^^^^^
    File "/snap/subiquity/6868/lib/python3.12/site-packages/subiquity/cmd/tui.py", line 159, in run_with_loop
      await subiquity_interface.run()
    File "/snap/subiquity/6868/lib/python3.12/site-packages/subiquity/client/client.py", line 426, in run
      await super().run()
    File "/snap/subiquity/6868/lib/python3.12/site-packages/subiquitycore/tui.py", line 390, in run
      await super().run()
    File "/snap/subiquity/6868/lib/python3.12/site-packages/subiquitycore/core.py", line 133, in run
      raise exc
    File "/snap/subiquity/6868/lib/python3.12/site-packages/subiquity/client/controllers/filesystem.py", line 300, in show_guided_and_redraw
      await self._guided_choice(choice)
  RuntimeError: coroutine raised StopIteration
                                                                                                            ^[[29;1R^[[29;106R
  Ubuntu Questing Quokka (development branch) ubuntu-server hvc

  
  Explaining whole scenario:

  When I tried to install my P11 lpar with Ubuntu with SAN disk
  1) 4 SAN disks are there
  2) I installed on mpatha (installation worked fine)
  3) I installed on mpathb (installation worked fine)
  4) When i rebooted the system connected to the console and then I tried to reinstall the system it gave the error message [-EBUSY] and then installation crashed

  My analysis:

  In the background, after each boot I was entering the shell and was checking for the multipath status:
  1) In the first attempt when i checked it gave all four disks
  2) After mpatha installation also all disks were listed in multipath -ll
  3) After mpathb installation also all disks were there
  4) When I tried the reinstallation after this I saw that multipath service itself gave the error as :

  [2168]: updated bindings file /etc/multipath/bindings
  [2168]: mpathb: addmap [0 230686720 multipath 1 queue_if_no_path 1 alua 2 1 ser>
  [2168]: libdevmapper: ioctl/libdm-iface.c(1995): device-mapper: reload ioctl on>
  [2168]: dm_addmap: libdm task=0 error: Device or resource busy
  [2168]: mpathb: ignoring map
  [2168]: mpathb: addmap [0 230686720 multipath 1 queue_if_no_path 1 alua 2 1 ser>
  [2168]: libdevmapper: ioctl/libdm-iface.c(1995): device-mapper: reload ioctl on>
  [2168]: dm_addmap: libdm task=0 error: Device or resource busy
  [2168]: mpathb: ignoring map
  : Started multipathd.service - Device-Mapper Multipath Device Controller.

  5) With multipath -ll I was not able to see mpathb there
  6) multipath service is not failing to restart but it is throwing this error message because mapping is not happening properly!
  I feel because of some stale metadata present on the mapathb at the time of installation which shouldn't have been there, it has happened.

  
  I tried this exact same scenario even on my P10 lpar which had 2 disks and I observed same kind of behavior! 

  Reproducibility with this exact scenario is 95%. 
  Reference bug is https://bugzilla.linux.ibm.com/show_bug.cgi?id=208604 but now the scenario has been changed!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/2133480/+subscriptions