Original question:
==================
How to remove LSM rootdg?
Answer:
=======
very carefully!
I did not get any replies from the list on this, but did get
a knowledgable gent at the support center. LSM does not have
hooks to let go of the last drive and go away itself, built in.
I had been loaned some drives to test with and so, when test
time was over, lsm had to be explained who was in charge. 8^D
I was warned that if this was not done correctly, the drives
left behind could be rendered useless (to osf, scu would not
be able to clear the area on the drive used by lsm).
Apparently, a person who got in this jam used a pc to do a low
level format, and recover.
Details (from the support center):
==================================
How do you remove LSM and re-use the disk?
1. Run volprint to get list of volume, media, and access names
#volprint -ht
2. Unmount all LSM volumes
3. Use the voledit command to remove the volume/volumes (rootdg is the default)
#voledit -g rootdg (diskgroup_name) -rf rm vol01 (volume_name)
NOTE: The -r option indicates recursive removal. So all plexes associated
with that volume, and all subdisks associated with the plexes, are
also removed.
The -f option forces removal.
4. Remove the specified disk from a disk group (rootdg is default)
#voldg -g rootdg (diskgroup_name) rmdisk rz0 (media_name)
NOTE: The last disk cannot be removed from a disk group. It is not
possible to remove the last disk containing a valid disk group
configuration or log copy from its disk group.
5. Remove disk access records, by name
#voldisk rm rz0 (disk accessname)
6. Remove the volboot file. The volboot file contains a host ID that is
used by the Logical Storage Manager to establish ownership of physical
disks. The volboot file also contains a list of disks to scan in search
of the rootdg disk group.
#rm /etc/vol/volboot
7. Remove LSM from /etc/inittab using the editor of choice. Remove the
line/lines that looks like the following:
lsm:23:wait:/sbin/lsmbstartup </dev/console >/dev/console 2>&1 ##LSM
vol:23:wait:/sbin/vol-reconfig </dev/console >/dev/console 2>&1 ##LSM
8. Reboot the system
NOTE: It is important that the system be re-booted if you wish to
re-use any of the disk that were previously LSM disk.
Until the kernel cache is updated (by rebooting) these disk
will still be in use by LSM.
If this is not done you may see the following message when
trying perform disklabel -rw rz0:
open partition would move or shrink, use alternate partition
You can zero out the disklabel but will not be able to
re-label until reboot is done. i.e. disklabel -z rz0.
9. You may then zero out and re-label the disklabel on disk that were
previously LSM disk.
#disklabel -z rz0
10. You may now also remove rootdg (this is not possible until system is
rebooted.)
#rm -r /dev/vol/rootdg
Comments (different subject):
=============================
The support guy that supplied this, said it would go into the STARS database,
and therefore, be available to DSNlink folks. We have DSNlink and I never use
it. Just to keep things interesting, let me say that Sun has their Q/A database
on the web with a searchable index.
http://sunsolve.sun.com/
I have used this database for years via cd media that sun sells, well worth
the bucks, and if I had to guess it cuts their support costs.
Does dec sell such a cd? You should. It would cut down of
the traffic here. I would look there first.
===============================================================
Ray Stell stellr_at_vt.edu (703) 231-4109 KE4TJC
Received on Tue May 23 1995 - 16:34:25 NZST