Showing results for 
Search instead for 
Did you mean: 

lock disk with Multipathd

Go to solution
D Block 2
Respected Contributor

lock disk with Multipathd

How did you setup up your lock disk ?

I was forced to mark the partition as type: 83 or Linux.

But, I have multipathd daemon and would prefer *not* to use fdisk command on a device /dev/sdo and marking type 83.

I prefer to use a multipathd's /dev/mapper/mpath# name instead of fdisk'ing a pseudo device named: /dev/sXX.

And, when I fdisk /dev/sXX, it then creates a 'p1' name suffix on /dev/mapper/mpath0p1.

Guess I don't understand why MC/SG can not use a standard named: /dev/mapper/mpath0 without a tag of 83 on a /dev/sXX device.

any comments?

Golf is a Good Walk Spoiled, Mark Twain.
Steven E. Protter
Exalted Contributor

Re: lock disk with Multipathd


Might want to configure your lock disk to be in LVM.

Steven E Protter
Owner of ISN Corporation
Serviceguard for Linux
Honored Contributor

Re: lock disk with Multipathd

Assuming you are referring to a Linux configuration (this forum) then there is no LVM support of Lock LUN. One reason we use that terminology is to differentiate it from the HP-UX version.

The certification matrix ( describes how you can use DM-MPIO with Lock LUN. Check the notes.

The reason has to do with the fact that Linux is a moving target and SGLX has been committed to backward compatibility and rolling upgrades. DM-MPIO is a relatively new feature while LockLUN has existed since nearly the first release of SGLX about 7 years ago. At that time the "83" partition type was required for some technical reasons.

The changes you describe require more thought and effort than you might think at first glance.