------- Comment From [email protected] 2025-02-18 13:33 EDT-------
Hi Olivier,

Please find my response inline:

(In reply to comment #51)
> Hello,
>
> I tried to reproduce the issue again today. Although this time the installer
> didn't crash ("$ vgs" and "$ lvs" returned valid information), I was in a
> scenario somewhat similar to what I described in comment 29:
>

We can still recreate the installer crash issue on our setups with 100% hit
rate.

> $ dmesg
> [ 1221.355112] device-mapper: table: 252:1: multipath: error getting device
> (-EBUSY)
> [ 1221.355116] device-mapper: ioctl: error adding target to table
> [ 1221.355552] device-mapper: table: 252:1: multipath: error getting device
> (-EBUSY)
> [ 1221.355554] device-mapper: ioctl: error adding target to table
> [ 1232.281218] device-mapper: table: 252:1: multipath: error getting device
> (-EBUSY)
> [ 1232.281223] device-mapper: ioctl: error adding target to table
> [ 1232.281668] device-mapper: table: 252:1: multipath: error getting device
> (-EBUSY)
> [ 1232.281670] device-mapper: ioctl: error adding target to table
>

Yes, we do observe the below log as well on our setup.

root@ubuntu:~# cat dmesg.log | grep -i device-mapper
// Before installer crash
[    0.185330] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. 
Duplicate IMA measurements will not be recorded in the IMA log.
[    0.185358] device-mapper: uevent: version 1.0.3
[    0.185473] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: 
[email protected]
[   12.287513] systemd[1]: Listening on dm-event.socket - Device-mapper event 
daemon FIFOs.
[   12.346628] systemd[1]: Starting multipathd.service - Device-Mapper 
Multipath Device Controller...
[   12.751023] device-mapper: multipath service-time: version 0.3.0 loaded
[   12.751190] device-mapper: table: 252:3: multipath: error getting device 
(-EBUSY)
[   12.751202] device-mapper: ioctl: error adding target to table
[   12.917597] device-mapper: table: 252:6: multipath: error getting device 
(-EBUSY)
[   12.917614] device-mapper: ioctl: error adding target to table
// After installer crash
[  133.571464] device-mapper: table: 252:12: multipath: error getting device 
(-EBUSY)
[  133.571471] device-mapper: ioctl: error adding target to table
[  133.572728] device-mapper: table: 252:12: multipath: error getting device 
(-EBUSY)
[  133.572731] device-mapper: ioctl: error adding target to table

> $ systemctl status multipath-tools
> * multipathd.service - Device-Mapper Multipath Device Controller
> Loaded: loaded (/usr/lib/systemd/system/multipathd.service; enabled; preset:
> enabled)
> Active: active (running) since Wed 2025-02-12 12:36:57 UTC; 20min ago
> TriggeredBy: * multipathd.socket
> Main PID: 911 (multipathd)
> Status: "up"
> Tasks: 7
> Memory: 20.3M (peak: 20.5M)
> CPU: 213ms
> CGroup: /system.slice/multipathd.service
> `-911 /sbin/multipathd -d -s
>
> Feb 12 12:36:57 ubuntu-server multipathd[911]: libdevmapper:
> ioctl/libdm-iface.c(1990): device-mapper: reload ioctl on mpatha (252:1)
> failed: Device or resource busy
> Feb 12 12:36:57 ubuntu-server multipathd[911]: dm_addmap: libdm task=0
> error: Device or resource busy
> Feb 12 12:36:57 ubuntu-server multipathd[911]: mpatha: ignoring map
> Feb 12 12:36:57 ubuntu-server multipathd[911]: sda: setting scsi timeouts is
> unsupported for protocol scsi:unspec
> Feb 12 12:36:57 ubuntu-server multipathd[911]: sdb: setting scsi timeouts is
> unsupported for protocol scsi:unspec
> Feb 12 12:36:57 ubuntu-server multipathd[911]: mpatha: addmap [0 25165824
> multipath 0 0 2 1 service-time 0 1 1 8:0 1 service-time 0 1 1 8:16 1]
> Feb 12 12:36:57 ubuntu-server multipathd[911]: libdevmapper:
> ioctl/libdm-iface.c(1990): device-mapper: reload ioctl on mpatha (252:1)
> failed: Device or resource busy
> Feb 12 12:36:57 ubuntu-server multipathd[911]: dm_addmap: libdm task=0
> error: Device or resource busy
> Feb 12 12:36:57 ubuntu-server multipathd[911]: mpatha: ignoring map
> Feb 12 12:36:57 ubuntu-server systemd[1]: Started multipathd.service -
> Device-Mapper Multipath Device Controller.
>

Yes.

root@ubuntu:~# systemctl status multipath-tools
* multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/usr/lib/systemd/system/multipathd.service; enabled; preset: 
enabled)
Active: active (running) since Tue 2025-02-18 14:17:45 UTC; 8min ago
TriggeredBy: * multipathd.socket
Main PID: 2112 (multipathd)
Status: "up"
Tasks: 7
Memory: 37.6M (peak: 45.6M)
CPU: 468ms
CGroup: /system.slice/multipathd.service
`-2112 /sbin/multipathd -d -s

Feb 18 14:17:45 ubuntu-server multipathd[2112]: dm_addmap: libdm task=0 error: 
Device or resource busy
Feb 18 14:17:45 ubuntu-server multipathd[2112]: mpatha: ignoring map
Feb 18 14:17:45 ubuntu-server multipathd[2112]: mpathb: addmap [0 230686720 
multipath 1 queue_if_no_path 1 alua 2 1 service-time 0 1 1 8:112 1 service-time 
0 1 1 8:48 1]
Feb 18 14:17:45 ubuntu-server multipathd[2112]: mpathc: addmap [0 230686720 
multipath 1 queue_if_no_path 1 alua 2 1 service-time 0 1 1 8:64 1 service-time 
0 1 1 8:128 1]
Feb 18 14:17:45 ubuntu-server multipathd[2112]: mpathd: addmap [0 230686720 
multipath 1 queue_if_no_path 1 alua 2 1 service-time 0 1 1 8:144 1 service-time 
0 1 1 8:80 1]
Feb 18 14:17:45 ubuntu-server multipathd[2112]: mpatha: addmap [0 230686720 
multipath 1 queue_if_no_path 1 alua 2 1 service-time 0 1 1 8:32 1 service-time 
0 1 1 8:96 1]
Feb 18 14:17:45 ubuntu-server multipathd[2112]: libdevmapper: 
ioctl/libdm-iface.c(1990): device-mapper: reload ioctl on mpatha (252:6) 
failed: Device or resource busy
Feb 18 14:17:45 ubuntu-server multipathd[2112]: dm_addmap: libdm task=0 error: 
Device or resource busy
Feb 18 14:17:45 ubuntu-server multipathd[2112]: mpatha: ignoring map
Feb 18 14:17:45 ubuntu-server systemd[1]: Started multipathd.service - 
Device-Mapper Multipath Device Controller.

>
> $ multipath
> 1232.283332 | sda: setting scsi timeouts is unsupported for protocol
> scsi:unspec
> 1232.283343 | sdb: setting scsi timeouts is unsupported for protocol
> scsi:unspec
> 1232.283368 | mpatha: addmap [0 25165824 multipath 0 0 2 1 service-time 0 1
> 1 8:0 1 service-time 0 1 1 8:16 1]
> 1232.283518 | libdevmapper: ioctl/libdm-iface.c(1990): device-mapper: reload
> ioctl on mpatha (252:1) failed: Device or resource busy
> 1232.283568 | dm_addmap: libdm task=0 error: Device or resource busy
> 1232.283604 | mpatha: ignoring map
> 1232.283906 | sda: setting scsi timeouts is unsupported for protocol
> scsi:unspec
> 1232.283909 | sdb: setting scsi timeouts is unsupported for protocol
> scsi:unspec
> 1232.283918 | mpatha: addmap [0 25165824 multipath 0 0 2 1 service-time 0 1
> 1 8:0 1 service-time 0 1 1 8:16 1]
> 1232.283963 | libdevmapper: ioctl/libdm-iface.c(1990): device-mapper: reload
> ioctl on mpatha (252:1) failed: Device or resource busy
> 1232.283988 | dm_addmap: libdm task=0 error: Device or resource busy
> 1232.284177 | mpatha: ignoring map
>

Yes, these errors are seen too.

root@ubuntu:~# multipath
// Before installer crash
cat multipath.log                                                               
                                                               ??
133.569339 | mpatha: addmap [0 230686720 multipath 1 queue_if_no_path 1 alua 2 
1 service-time 0 1 1 8:32 1 service-time 0 1 1 8:96 1]
133.569582 | libdevmapper: ioctl/libdm-iface.c(1990): device-mapper: reload 
ioctl on mpatha (252:12) failed: Device or resource busy
133.569674 | dm_addmap: libdm task=0 error: Device or resource busy
133.569713 | mpatha: ignoring map
133.570677 | mpatha: addmap [0 230686720 multipath 1 queue_if_no_path 1 alua 2 
1 service-time 0 1 1 8:32 1 service-time 0 1 1 8:96 1]
133.570841 | libdevmapper: ioctl/libdm-iface.c(1990): device-mapper: reload 
ioctl on mpatha (252:12) failed: Device or resource busy
133.570920 | dm_addmap: libdm task=0 error: Device or resource busy
133.570948 | mpatha: ignoring map

// After installer crash
543.255293 | mpatha: addmap [0 230686720 multipath 1 queue_if_no_path 1 alua 2 
1 service-time 0 1 1 8:32 1 service-time 0 1 1 8:96 1]
543.255485 | libdevmapper: ioctl/libdm-iface.c(1990): device-mapper: reload 
ioctl on mpatha (252:12) failed: Device or resource busy
543.255577 | dm_addmap: libdm task=0 error: Device or resource busy
543.255619 | mpatha: ignoring map
543.256642 | mpatha: addmap [0 230686720 multipath 1 queue_if_no_path 1 alua 2 
1 service-time 0 1 1 8:32 1 service-time 0 1 1 8:96 1]
543.256753 | libdevmapper: ioctl/libdm-iface.c(1990): device-mapper: reload 
ioctl on mpatha (252:12) failed: Device or resource busy
543.256811 | dm_addmap: libdm task=0 error: Device or resource busy
543.256838 | mpatha: ignoring map

>
> Could you check if you're seeing any of the above errors? Ideally, would you
> mind sharing the journal logs + dmesg.log?
>

Sure, I'll attach these logs.

> Thank you,
> Olivier

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

Title:
  ubuntu installation failing for systems having SAN disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2080474/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to