Should I use devices in /dev/mpath directly?

Solution Verified - Updated -

Issue

  • Should I use devices in /dev/mpath directly ?

  • When creating partitions on newly-added multipath devices, the system doesn't update those partition entries in /dev/mpath.

  • There are missing partition devices in /dev/mpath:

# ls -al /dev/mpath*

lrwxrwxrwx  1 root root     8 Dec  3 19:19 mpath0 -> ../dm-25
lrwxrwxrwx  1 root root     8 Dec  3 19:19 mpath0p1 -> ../dm-51
lrwxrwxrwx  1 root root     8 Dec  3 19:19 mpath1 -> ../dm-26
lrwxrwxrwx  1 root root     8 Dec  3 19:19 mpath1p1 -> ../dm-59
...
lrwxrwxrwx  1 root root     9 Jan 31 09:53 mpath613 -> ../dm-105
lrwxrwxrwx  1 root root     9 Jan 31 09:53 mpath614 -> ../dm-106
lrwxrwxrwx  1 root root     9 Jan 31 09:53 mpath615 -> ../dm-107
lrwxrwxrwx  1 root root     9 Jan 31 09:53 mpath616 -> ../dm-108

Environment

  • Red Hat Enterprise Linux 5
  • device-mapper-multipath
  • Storage added after system boot

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content