Using /dev/mapper is always how I've seen it done. /dev/mpath/* looks to
be just a symlink to /dev/dm-? device nodes which are, in turn, device
nodes with identical major/minor numbers as /dev/mapper/*.

Why /dev/mpath/* is even there, I'm not sure.

Gerrard Geldenhuis wrote:
> Hi
>
> I have recently setup new san storage using multipath to access it.
>
>
>
> when adding an alias multipath.conf
>
>
>
> multipaths {
>
>      multipath {
>
>           wwid             350002ac014??????
>
>           alias             authdb-storage
>
>           }
>
>      }
>
>
>
>
>
> The alias gets put in /dev/mapper/authdb-storage
>
> /dev/mpath/<wwid> might be more accurate or definitive.
>
>
>
> My question is simple, which is the most approprate path to access the
> storage from,
>
> /dev/mapper/ or /dev/mpath/ ?
>
>
>
> Regards
>
>
> ___________________________________________________________________________
>
> Inbound Email has been scanned by Nexa Technologies Email Security Systems.
> ___________________________________________________________________________
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> rhelv5-list mailing list
> rhelv5-list@(protected)
> https://www.redhat.com/mailman/listinfo/rhelv5-list

--
Jeff Macfarland (jmacfarland@(protected))
Nexa Technologies - 972.747.8879
Systems Administrator
GPG Key ID: 0x5F1CA61B
GPG Key Server: hkp://wwwkeys.pgp.net

_______________________________________________
rhelv5-list mailing list
rhelv5-list@(protected)
https://www.redhat.com/mailman/listinfo/rhelv5-list