Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am trying to map Clariion LUN #s to physical volumes inside Volume groups I can see out put like.
--- Physical volume ---
PV Name /dev/sdk1
VG Name vgDATA
PV Size 46.87 GB / not usable 32.00 MB
Allocatable yes (but full)
PE Size (KByte) 32768
Total PE 1499
Free PE 0
Allocated PE 1499
PV UUID qLtPDS-j9cl-0cIN-1AAR-eS3w-AikS-vcsBm5
his requires that you install EMC Powerpath software onto the Linux system. EMC Powerpath is a licensed software (meaning you have to pay for it AND continue to pay for it in support to keep it licensed). EMC loves to audit its customers because they've given up trying to make their money by providing good products and support.
You might want to investigate using the native Linux multipath tool for the same purpose as Powerpath as it does not require any extra licensing from EMC and also works with other disk arrays such as Hitachi's. (Type "man multipath" for more details.)
If you have do have Powerpath installed and must use it you can use the "powermt" command to examine/configure setup for your presented disks. If you type "man powermt" you will see details of the command. A couple of commands:
Outputs basic information and lets you know if all your paths are optimal
powermt display dev=all
Gives more detail similar to what you put in your post.
Note that your original disk is sdk and the example output you listed doesn't included sdk. I'm assuming these were just examples. You can't force a path that is not to the same physical disk (LUN) to be in the same multiple-path pseudo device but can add new paths if required. Basically both powermt and multipath can determine what is on the disks they see and add it to their configs automatically when you use the correct commands to rescan.
LVM doesn't rename disks. It uses them as PVs (physical volumes) in the VGs (volume groups). You're sort of putting the cart before the horse.
You need to first present the disks (LUNS) to the OS. (e.g. /dev/sdc, /dev/sdj, /dev/sdq, /dev/sdx, /dev/sdk).
You then put the disks into your powerpath or multipath config. It is the emcpower[alpha] pseudo device for powerpath (or the dm [mpath] device for multipath) that is comprised of the original disks.
You then use the emcpower (or multipath) devices as your PV when you do the vgcreate. You should NOT use the underlying disks (/dev/sdk, /dev/sdc, /dev/sdo) as PV because those do not have multiple paths - they are single paths and it is powerpath (or multipath) that gives you the multiple path device. Any action you do to the multiple path device will work if any of the paths beneath it go away so long as one remains.
So in your original example your pseudo (multiple path) device is /dev/emcpowerh. This would be what you did the pvcreate on and what you would specify as a PV when you did the vgcreate. You should NOT use from that example ANY of the disks (sdc, sdj, sdq or sdx). If you use the pseduo device then if sdc, sdq and sdx all went away for some reason everything would continue to work because sdj is still there. If on the other hand you had specified sdq and it went away for some reason then things would break even though sdc, sdj and sdx are still OK because you didn't tell it to use the multiple path device but rather a single path.
Additionally Linux does sometimes rename paths to disks (e.g. sdc MIGHT become sdk on a future reboot) but the multipathing software would keep track of the underlying disks and so long as you'd specified the pseudo device
everything should continue to work.
Did you try running the powermt commands I gave in my prior post?
Did you review the powermt man page as I suggested?
Last edited by MensaWater; 09-05-2012 at 12:28 PM.
The "powermt display dev=all" shows you which Clariion LUN is associated with which emcpower[alpha] pseudo device and also shows you which /dev/sd* devices comprise the pseudo device.
What you wrote reminded me that once I wanted to change the actual pseudo device name because I wanted to hosts in a cluster to have the same name for the same Clariion LUNs. The command I used for that was:
"emcpadm renamepseudo -s emcpower[a-z] -t emcpower[a-z]" to reassign which pseudo device letter is used for a specific LUN.
e.g. You have LUN 102 showing up as emcpowerg but since it is 3rd LUN you want it to be emcpowerc instead:
emcpadm renamepseudo -s emcpowerg -t emcpowerc
If you have Navisagent installed and running on the Linux host you can also use navicli to see the LUN/pseudo device info:
/opt/Navisphere/bin/navicli lunmapinfo <IP OF CLARIION SPA or SPB>