I sent a PULL request to the fork source.
https://github.com/xapi-project/sm/pull/576
Posts
-
RE: multipath.conf is incorrect
-
Resolving SR Not Unpluggable After NBD Backup Errors
I noticed that sr could not unplug after the NBD backup failed.
I'll blurt out the solution. There may be others out there, but I hope it helps someone.
I assume this is because when an NBD backup makes a vbd connection and exits with an error, the vbd connection is not broken.# xe pbd-unplug uuid=79a53996-60d7-8fc0-1f8b-ba1e30b5d0ce This operation cannot be performed because this VDI is in use by some other operation vdi: 41b7ff1a-05be-43db-a592-849f9ab30444 (***************) operation: 071e6f0b-9670-44b6-b455-b8d1319da28b (***************)
# xe vdi-param-list uuid=071e6f0b-9670-44b6-b455-b8d1319da28b | grep vbd-uuids vbd-uuids (SRO): 61a50e07-51c4-3476-d47c-45e756f127fe
Unplug the displayed vbd-uuids.
# xe vbd-unplug uuid=61a50e07-51c4-3476-d47c-45e756f127fe
-
RE: multipath.conf is incorrect
Thanks to everyone, I was able to complete it.
Thank you very much!! -
multipath.conf is incorrect
Hello,
The QNAP setting in multipath.conf is incorrect. The settings cannot be called correctly because the product attribute is different. It seems to work with default values.
I will feed back my experience to XCP-NG project.
product attribute - [Underbar is incorrect. Space is correct]
/etc/multipath.xenserver/multipath.conf.old
device { vendor "QNAP" product "iSCSI_Storage" }
/etc/multipath.xenserver/multipath.conf
device { vendor "QNAP" product "iSCSI Storage" }
I was editing multipath.conf to give priority to multipathing sessions.
I started debugging because the settings didn't apply. You have noticed a difference in the call string "iSCSI Storage".[16:30 xxxxxxxxx etc]# multipath -ll xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx dm-0 QNAP ,iSCSI Storage size=20T features='1 queue_if_no_path' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=9 status=active | `- 9:0:0:0 sdb 8:16 active ready running `-+- policy='round-robin 0' prio=1 status=enabled `- 10:0:0:0 sdc 8:32 active ready running
By replacing the underscore with a space, the setting is now recognized correctly and the session can be given priority.
device { vendor "QNAP" product "iSCSI Storage" path_grouping_policy "failover" path_selector "round-robin 0" path_checker readsector0 prio weightedpath prio_args "hbtl 9:0:0:0 9 10:0:0:0 1" uid_attribute ID_SERIAL }
My Storage: TS-432PXU-RP
Version: 5.0.0.1828 Build 20211020