From: Pat OBrien (Pat.OBrien@choicepoint.com)
Date: Mon Nov 10 2003 - 17:53:40 EST
One response to check /etc/inittab to verify lsm startup commands are there. They are not, but support is reviewing becuase it would seem the only proper method of unencaping a root disk is to volunroot it.
-----Original Message-----
From: Pat OBrien [mailto:Pat.OBrien@choicepoint.com]
Sent: Sunday, November 09, 2003 3:31 PM
To: Tru64-unix-managers@ornl.gov
Subject: 5.1B LSM ISSUE
I developed a procedure create a alternate boot disk or allow a admin to resize a root disk a long time ago (osf 3.2)which has just started to fail me. I have always mirrored my root disk with host based lsm mirriroing and have almost always utilized ufs filesystems. When ever a system was going to be upgraded or the root disk was running short of space, I would dust off this procedure. The crux of this procedure is that I add a 3rd disk, partition this disk in my chosen manner with a,b, & g partitions(usr & var are in g), create ufs filesystems for partition a and g and set the b to be swap, mount a partition to a mount point vdump root to this partition and the mount usr and replicated, change the required files and boot this adhoc root disk. When this disk booted successfully, I can then remove previous root disks from lsm config without unencapping the root disk, replace disks with bigger ones if need, or just re-allocate as required and then reverse the process to one of the previously mirrored disk
s. Once upgrade if being performed was complete, re-mirror root disks with lsm. A few months ago I discovered that once a disk had been encapsulated, several files are left behind in the etc-vol area. removing these previous to another encap would allow a 5.1 encap of say dsk0 to preoceed, however under 5.1B, just a mes results. Performing a volreconfig will enacap the root partition and reboot leaving the lsm private area swap and usr un encapsulated. re-running volreconfig will then encapsulate swap and reboot, however 2 more volreconfig did no more. Bring the system down and back up to single user, perform lsmbstartup, bcheck rc and volreconfig got the g usr partition done, but the h partitin is not done. Truthfully this is all I think that I need because have 4 other lsm sliced disks in the system, but I think volrootmir is not going to like this config. I unencap swap to get the lsm private area define and tip toe through a war zone of land mines to make this work. Any ideas for a easier me
thod?
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:43 EDT