System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Forcing /dev/mpath/mpath* aliases

 
SOLVED
Go to solution
Anthony Dyson
Occasional Visitor

Forcing /dev/mpath/mpath* aliases

We used to have 16 LUN's where the numeric component of the /dev/mp-* -> /dev/mpath/mpath* symlinks all matched & were persistent over reboots. After adding 8 new LUNS, the symlinks have been reordered. For example, /dev/dm-0 is now symlinked to /dev/mpath/mpath8.

Does anyone know how to force the links back to the way they were before? The intention would be to make the new LUN's /dev/mp-16 >> 23 with corresponding /dev/mpath/mpath16 >> 23 symlinks.
4 REPLIES
skt_skt
Honored Contributor

Re: Forcing /dev/mpath/mpath* aliases

which linux version? could u post "/etc/modprobe.conf" and "rpm -qa|grep -i mapper"?

Do you use power path here?which HBA cards are used?

what real impact do you have due to the said change?
Randy Jones_3
Trusted Contributor
Solution

Re: Forcing /dev/mpath/mpath* aliases

Bindings of mpath IDs to volumes are retained in /var/lib/multipath/bindings (on my RHEL systems anyway) and new bindings to previously unknown volumes are assigned new entries at the bottom of the file. The lower-numbered path IDs you're looking for are bound to obsolete volumes.

Delete the file and let multipath recreate it, or edit it.
Anthony Dyson
Occasional Visitor

Re: Forcing /dev/mpath/mpath* aliases

Randy Jones: thanks for that info. I'd become fairly sure that the mpath -> WWID relationships in the bindings file were really the important consideration, & that the "/dev/dm-*" devices are intentionally mutable & we shouldn't care. Now I won't try to mount a /dev/dm-* device again.
skt_skt
Honored Contributor

Re: Forcing /dev/mpath/mpath* aliases

dont you use VG(LVM) ?Just wondering why to mount using a dm device file.