Problem with multipath, wwid not in wwids file

mishki

New Member
May 1, 2020
8
0
1
33
What am I doing wrong?

1 SAN - 2 ports in Port Group with different IP and IQN
172.16.20.228:3260,3 iqn.2000-09.com.fujitsu:storage-system.eternus-dxl:002c0534
172.16.20.229:3260,4 iqn.2000-09.com.fujitsu:storage-system.eternus-dxl:002c0535

Proxmox - added iSCSI, add LVM volume from iSCSI
172.16.20.149

/etc/multipath.conf

Code:
defaults {
    user_friendly_names    yes
        polling_interval        2
        path_selector           "round-robin 0"
        path_grouping_policy    multibus
        path_checker            readsector0
        uid_attribute          "ID_SERIAL"
        rr_min_io               100
        failback                immediate
        no_path_retry           queue
}
blacklist {
        wwid .*
}
blacklist_exceptions {
        wwid "3600000e00d2c0000002c014d00020000"
}
multipaths {
  multipath {
        wwid "3600000e00d2c0000002c014d00020000"
        alias mpath0
  }
}
# multipath -ll

nothing..


# multipath -v3

Code:
===== paths list =====
uuid                              hcil     dev dev_t pri dm_st chk_st vend/pro
3600000e00d2c0000002c014d00020000 33:0:0:1 sdb 8:16  50  undef undef  FUJITSU,
3600000e00d2c0000002c014d00020000 34:0:0:1 sdc 8:32  50  undef undef  FUJITSU,
May 23 01:37:48 | libdevmapper version 1.02.155 (2018-12-18)
May 23 01:37:48 | DM multipath kernel driver v1.13.0
May 23 01:37:48 | sdb: udev property ID_WWN whitelisted
May 23 01:37:48 | sdb: wwid 3600000e00d2c0000002c014d00020000 whitelisted
May 23 01:37:48 | wwid 3600000e00d2c0000002c014d00020000 not in wwids file, skipping sdb
May 23 01:37:48 | sdb: orphan path, only one path
May 23 01:37:48 | sysfs prioritizer refcount 2
May 23 01:37:48 | sdc: udev property ID_WWN whitelisted
May 23 01:37:48 | sdc: wwid 3600000e00d2c0000002c014d00020000 whitelisted
May 23 01:37:48 | wwid 3600000e00d2c0000002c014d00020000 not in wwids file, skipping sdc
May 23 01:37:48 | sdc: orphan path, only one path
May 23 01:37:48 | sysfs prioritizer refcount 1
May 23 01:37:48 | unloading sysfs prioritizer
May 23 01:37:48 | unloading const prioritizer
May 23 01:37:48 | unloading tur checker
# lsscsi
Code:
[2:0:0:0]    disk    VMware   Virtual disk     2.0   /dev/sda
[3:0:0:0]    cd/dvd  NECVMWar VMware SATA CD00 1.00  /dev/sr0
[33:0:0:1]   disk    FUJITSU  ETERNUS_DXL      1088  /dev/sdb
[34:0:0:1]   disk    FUJITSU  ETERNUS_DXL      1088  /dev/sdc
# /lib/udev/scsi_id -g -d /dev/sdb
3600000e00d2c0000002c014d00020000

# /lib/udev/scsi_id -g -d /dev/sdc
3600000e00d2c0000002c014d00020000

# pvesm scan lvm
Code:
WARNING: Not using device /dev/sdc for PV MdueSG-N3wH-J11f-8BNN-Ddrq-CEY2-LPTJk9.
  WARNING: PV MdueSG-N3wH-J11f-8BNN-Ddrq-CEY2-LPTJk9 prefers device /dev/sdb because device was seen first.
lvm
pve

If I leave only one port in the Port Group, then there is no problem.
 
Last edited:

mishki

New Member
May 1, 2020
8
0
1
33
There is no difference in the output of the command multipath -v3, is there something in the file wwids or not.

/etc/multipath/wwids

Code:
# Multipath wwids, Version : 1.0
# NOTE: This file is automatically maintained by multipath and multipathd.
# You should not need to edit this file in normal circumstances.
#
# Valid WWIDs:

3600000e00d2c0000002c014d00020000
 

LnxBil

Famous Member
Feb 21, 2015
4,991
515
133
Germany
Have you restarted the multipath daemon? I still don't get why people blacklist all and then reenable the wwids. I just blacklist my local devices and never had any problem with it. It's much easier to debug.
 

oduL

New Member
May 24, 2020
2
1
3
Dear Mishki,

I just set-up a multipath to an iSCSI target yesterday and get it to work successfully.
Steps I followed :
1. Created "/etc/multipath.conf" based on the example provided in the Proxmox Wiki.
Minor differences I see with yours is missing "path_checker readsector0" in the "defaults" section in my case.
2. Ran "systemctl restart multipath-tools.service" to restart service
3. When checking status with "/etc/multipath# multipath -ll", I also obtained "May 23 15:37:44 | wwid 36e843b696e00140d1af8d4937db522d7 not in wwids file, skipping sde" error
To solve this, you have to use "multipath -a [dev]".
in my case: "multipath -a /dev/sde"
-> which returned: "wwid '36e843b696e00140d1af8d4937db522d7' added"
In your case should be "multipath -a /dev/sdb" (no need to do for both sdb and sdc, since both have the same wwid...)

After this, final check:
- "multipath -c /dev/sde" returns "DM_MULTIPATH_DEVICE_PATH="1"" (was returning "0" previously) -> OK
- "multipath -ll" returns:
Code:
mpath0 (36e843b696e00140d1af8d4937db522d7) dm-0 QNAP,iSCSI Storage
size=500G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
`-+- policy='round-robin 0' prio=50 status=active
  |- 10:0:0:0   sde     8:64  active ready running
  `- 11:0:0:0   sdf     8:80  active ready running
-> OK
- "multipath -v3" returns:
Code:
(...)
May 23 15:41:32 | sde: udev property ID_WWN whitelisted
May 23 15:41:32 | sde: wwid 36e843b696e00140d1af8d4937db522d7 whitelisted
May 23 15:41:32 | sdf: udev property ID_WWN whitelisted
May 23 15:41:32 | sdf: wwid 36e843b696e00140d1af8d4937db522d7 whitelisted
May 23 15:41:32 | alua prioritizer refcount 2
(...)
-> OK

Hoping this is helpful.
 
  • Like
Reactions: mishki

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!