Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

ubuntu 2204 kvm multipath iscsi reservation issue

Pages: 1 2

daniel.shafer
8 Posts
March 14, 2025, 12:09 pm

Using this latest multipath set of directives, two paths to a volume work fine.

Four paths throws a reservation error soon as I try to build a vm in the volume:

Mar 14 06:05:05 ftc-mvm-010 kernel: [63531.465291] sd 3:0:0:0: reservation conflict
Mar 14 06:05:05 ftc-mvm-010 kernel: [63531.465323] sd 3:0:0:0: [sdf] tag#75 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Mar 14 06:05:05 ftc-mvm-010 kernel: [63531.465328] sd 3:0:0:0: [sdf] tag#75 CDB: Write(16) 8a 00 00 00 00 03 28 88 21 18 00 00 01 80 00 00
Mar 14 06:05:05 ftc-mvm-010 kernel: [63531.465331] reservation conflict error, dev sdf, sector 13564911896 op 0x1:(WRITE) flags 0x4a00 phys_seg 48 prio class 0
Mar 14 06:05:05 ftc-mvm-010 kernel: [63531.466777] reservation conflict error, dev dm-1, sector 13564911896 op 0x1:(WRITE) flags 0x800 phys_seg 48 prio class 0
Mar 14 06:05:05 ftc-mvm-010 kernel: [63531.467048] dm-1: writeback error on inode 1695613986, offset 0, sector 13564911896
Mar 14 06:05:05 ftc-mvm-010 kernel: [63531.467756] sd 4:0:0:0: reservation conflict
Mar 14 06:05:05 ftc-mvm-010 kernel: [63531.468349] sd 4:0:0:0: [sdg] tag#107 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Mar 14 06:05:05 ftc-mvm-010 kernel: [63531.468394] sd 4:0:0:0: [sdg] tag#107 CDB: Write(16) 8a 00 00 00 00 00 00 00 fe 48 00 00 00 30 00 00
Mar 14 06:05:05 ftc-mvm-010 kernel: [63531.468406] reservation conflict error, dev sdg, sector 65096 op 0x1:(WRITE) flags 0x4200 phys_seg 6 prio class 0
Mar 14 06:05:05 ftc-mvm-010 kernel: [63531.468909] reservation conflict error, dev dm-1, sector 65096 op 0x1:(WRITE) flags 0x0 phys_seg 6 prio class 0
Mar 14 06:05:05 ftc-mvm-010 kernel: [63531.469419] gfs2: fsid=ftc_mvm_cluster_02:mvm2_iscsi_02.0: Error 6 writing to journal, jid=0
Mar 14 06:05:05 ftc-mvm-010 kernel: [63531.469843] gfs2: fsid=ftc_mvm_cluster_02:mvm2_iscsi_02.0: about to withdraw this file system
Mar 14 06:05:11 ftc-mvm-010 kernel: [63536.907971] gfs2: fsid=ftc_mvm_cluster_02:mvm2_iscsi_02.0: Requesting recovery of jid 0.
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.392358] gfs2: fsid=ftc_mvm_cluster_02:mvm2_iscsi_02.0: Journal recovery complete for jid 0.
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.392373] gfs2: fsid=ftc_mvm_cluster_02:mvm2_iscsi_02.0: Glock dequeues delayed: 0
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.397412] gfs2: fsid=ftc_mvm_cluster_02:mvm2_iscsi_02.0: telling LM to unmount
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.397822] dlm: mvm2_iscsi_02: leaving the lockspace group...
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.431667] gfs2: fsid=ftc_mvm_cluster_02:mvm2_iscsi_02.0: recover_prep ignored due to withdraw.
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.432027] dlm: mvm2_iscsi_02: group event done 0
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.432451] dlm: mvm2_iscsi_02: release_lockspace final free
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.432513] gfs2: fsid=ftc_mvm_cluster_02:mvm2_iscsi_02.0: File system withdrawn
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.432944] CPU: 1 PID: 561631 Comm: gfs2_logd/ftc_m Not tainted 6.8.0-52-generic #53~22.04.1-Ubuntu
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.432948] Hardware name: HP ProLiant XL170r Gen9/ProLiant XL170r Gen9, BIOS U14 08/29/2024
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.432950] Call Trace:
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.432953] <TASK>
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.432958] dump_stack_lvl+0x76/0xa0
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.432976] dump_stack+0x10/0x20
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.432982] gfs2_withdraw+0xd5/0x160 [gfs2]
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.433028] gfs2_logd+0x1ef/0x330 [gfs2]
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.433045] ? __pfx_autoremove_wake_function+0x10/0x10
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.433051] ? __pfx_gfs2_logd+0x10/0x10 [gfs2]
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.433068] kthread+0xf2/0x120
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.433073] ? __pfx_kthread+0x10/0x10
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.433075] ret_from_fork+0x47/0x70
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.433078] ? __pfx_kthread+0x10/0x10
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.433080] ret_from_fork_asm+0x1b/0x30
Mar 14 06:05:11 ftc-mvm-010 kernel: [63537.433084] </TASK>

 

The multipath directives are the issue, I just wish I knew what settings your team have blessed in the past that work for a petasan array.

I'm running with two paths now and it's acceptable, but itt's half the speed I see with four paths.

#11

admin
2,957 Posts
March 14, 2025, 3:17 pm

very good it now works with 2 paths per disk.

i do not know if mvm (morpheus) is the one that setup the multipathing incorrectly in the first place, if so i would recommend you give give them feedback on this.

if you want to use 4 paths, check the output of

multipath -ll

#12
Pages: 1 2