Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing LUN removal from kernel after removal of disk #176

Open
netadair opened this issue Feb 1, 2024 · 1 comment
Open

Missing LUN removal from kernel after removal of disk #176

netadair opened this issue Feb 1, 2024 · 1 comment
Assignees
Labels
Diagnose Diagnose/Discuss a issue or concern Question Further information is requested wontfix This will not be worked on

Comments

@netadair
Copy link

netadair commented Feb 1, 2024

Hi all,
I'm not sure if this is more a Proxmox than a plugin problem, but when (for some reason, I'm still having trouble because qemu and vma as of Proxmox usage does not support CHAP auth), a disk is removed, the kernel is not notified.
This yields lots(!) of error messages all 10 seconds when Proxmox does a rescan of the iscsi target.
Example:

new volume ID is 'truenas-113:vm-100-disk-0'
new volume ID is 'truenas-113:vm-100-disk-1'
Rescanning session [sid: 3, target: iqn.xxx:storage01, portal: xxx,3260]
sh: 1: /usr/sbin/multipath: not found
map 'drive-scsi0' to 'iscsi://xxx/iqn.xxx:storage01/1' (write zeros = 1)
Rescanning session [sid: 3, target: iqn.xxx:storage01, portal: xxx,3260]
sh: 1: /usr/sbin/multipath: not found
map 'drive-scsi1' to 'iscsi://xxx/iqn.xxx:storage01/2' (write zeros = 1)
vma: can't open file iscsi://xxx/iqn.xxx:storage01/1 - iSCSI: Failed to connect to LUN : Failed to log in to target. Status: Authentication failure(513)
/bin/bash: line 1: 1870707 Broken pipe             zstd -q -d -c /var/lib/vz/dump/vzdump-qemu-102-2024_01_30-19_41_59.vma.zst
     1870708 Trace/breakpoint trap   | vma extract -v -r /var/tmp/vzdumptmp1870698.fifo - /var/tmp/vzdumptmp1870698
temporary volume 'truenas-113:vm-100-disk-1' sucessfuly removed
temporary volume 'truenas-113:vm-100-disk-0' sucessfuly removed

will give

Jan 31 21:44:17 pve-118 kernel: sd 4:0:0:1: [sdh] Unit Not Ready
Jan 31 21:44:17 pve-118 kernel: sd 4:0:0:1: [sdh] Sense Key : Illegal Request [current]
Jan 31 21:44:17 pve-118 kernel: sd 4:0:0:1: [sdh] Add. Sense: Logical unit not supported
Jan 31 21:44:17 pve-118 kernel: sd 4:0:0:1: [sdh] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
Jan 31 21:44:17 pve-118 kernel: sd 4:0:0:1: [sdh] Sense Key : Illegal Request [current]
Jan 31 21:44:17 pve-118 kernel: sd 4:0:0:1: [sdh] Add. Sense: Logical unit not supported
Jan 31 21:44:17 pve-118 kernel: sd 4:0:0:1: [sdh] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK
Jan 31 21:44:17 pve-118 kernel: sd 4:0:0:1: [sdh] Sense Key : Illegal Request [current]
Jan 31 21:44:17 pve-118 kernel: sd 4:0:0:1: [sdh] Add. Sense: Logical unit not supported

for each LUN and every 10 seconds.

@TheGrandWazoo TheGrandWazoo self-assigned this Mar 22, 2024
@TheGrandWazoo TheGrandWazoo added Question Further information is requested Diagnose Diagnose/Discuss a issue or concern labels Mar 22, 2024
Copy link

stale bot commented May 22, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Diagnose Diagnose/Discuss a issue or concern Question Further information is requested wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants