Root Disk Setup

[Mark Mitchell]

How many of you use the lvol1 to lvol8 to name your volumes on install. I wrote a script to automate the mirror process and just wanted to get an idea if its nessasary to have it search for the lvol names or hard code it. Otherwise finding the root swap is a pain, I am looking at a
#pvdisplay -v $ROOTDISK|grep -v current|grep -v stale|grep -v Name|awk {'print $1'}|cut -f 4 -d /
And then I am tring to avoid a tmp file for that out put and the such.
So how many of you have special names for the lvols? Save me a lot of trouble....

[Sundar_7]

As far as VG00 lvols, I dont prefer customizing the name.

[A. Clay Stephenson]

Well, lvol1, lvol2, lvol3, ... is by far the most common but I know of a few whacko's who, for example, put everything except /stand and primary swap in /. There are no other LVOL's. It's even conceivable that / could also be the boot LVOL -- if / is configured as an hfs filesystem. So the rigorous solution requires that you do an lvlnboot -v and ask the system itself. After /stand, primary swap, and / are mirrored in that order the order of the other lvextends is not critical so a vgdisplay -v | grep "LV Name" should serve as a filter.

[A. Clay Stephenson]

I should add that the way to avoid all this nonsense is to set standards as in "Thou shalt lay out boot disks thusly:" and then it is perfectly acceptable to hardcode LVOL names. That way, you always know, for example, that /usr is lvolxx. Of course, it is also necessary that said standards be adhered to ---- I find baseball bats to be useful for that.