On Fri, 2021-10-08 at 20:24 +0800, chengjike wrote: > After "Native NVME Multipath" is configured, > the content displayed is incorrect when you run "multipath -ll" > command. > Each NVME devices have the same path name. For example: > > [root@localhost home]# multipath -ll > eui.710032e8fb22a86c24a52c1000000db8 [nvme]:nvme1n1 NVMe,Huawei- > XSG1,1000001 > size=10485760 features='n/a' hwhandler='ANA' wp=rw > > -+- policy='n/a' prio=50 status=optimized > > `- 1:4:1 nvme1c4n1 0:0 n/a optimized live > `-+- policy='n/a' prio=50 status=optimized > `- 1:9:1 nvme1c9n1 0:0 n/a optimized live > eui.710032e8fb22a86b24a52c7c00000db7 [nvme]:nvme1n2 NVMe,Huawei- > XSG1,1000001 > size=10485760 features='n/a' hwhandler='ANA' wp=rw > > -+- policy='n/a' prio=50 status=optimized > > `- 1:4:1 nvme1c4n1 0:0 n/a optimized live > `-+- policy='n/a' prio=50 status=optimized > `- 1:9:1 nvme1c9n1 0:0 n/a optimized live > [root@localhost home]# > > The logical paths of "nvme1n1" and "nvme1n2" are both "nvme1c4n1" and > "nvme1c9n1". > So when multipath-tools aggregates disks, use "nvme_ns_head- > >instance" for matching. > such as ,Use "b" in "nvmeanb" string to match "z" in > "nvmexcynz"(a,b,x,y,z can be any number), > and if "b" and "z" are the same, they are related. > > Signed-off-by: chengjike <chengjike.cheng@xxxxxxxxxx> Reviewed-by: Martin Wilck <mwilck@xxxxxxxx> Thanks!! -- dm-devel mailing list dm-devel@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/dm-devel
