From: rob.de.langhe@belgacom.be
Date: Thu Feb 03 2005 - 07:12:16 EST
Since I have not got a single reply yet for this question (apart from
the obvious "out-of-office"), I dare to re-post it ...
-----Original Message-----
From: sunmanagers-bounces@sunmanagers.org
[mailto:sunmanagers-bounces@sunmanagers.org] On Behalf Of
rob.de.langhe@belgacom.be
Sent: 02 February 2005 13:55
To: sunmanagers@sunmanagers.org
Subject: upgrade to VxVM 4.0 : existing disks are re-discovered, but as
type=auto instead of type=sliced
Hi,
while checking out the upgrade procedure of VxVM from versions pre-4.0
towards version 4.0, I encountered the following annoying new default
behaviour of VxVM 4.0 :
1) assume we start from an existing installation with VxVM 3.5, with
both simple partitions of the boot disks configured in VxVM 3.5 as
"rootdg" disks (I know, "rootdg" requirements are different in 4.0) as
well as full (slice "s2") disks configured in either "rootdg" or other
disk groups
2) we perform the VxVM upgrade to version 4.0 as per the installation
guide
3) the existing disks 'discovered' by VxVM 4.0 at startup time (I assume
this is done by "vxconfigd") are now no longer of type "sliced" (as in
VxVM 3.5), but of type "auto:none"
Altough this is correct behaviour of 4.0 (cfr man pages), this renders
my simple-slice 'disks' of which the "rootdg" was made off no longer
immediately recognizable.
As a result, my "rootdg" cannot be activated yet.
I found the cheaty way to get around this, on a per-disk basis :
After upgrade to 4.0 :
# vxdisk list
c1t0d0s2 auto:none
# vxdisk rm c1t0d0s2
# vxdisk define c1t0d0s4 type=simple
# vxdisk list
c1t0d0s4 simple
# vxconfigd -k
#
At this point, my "rootdg" is correctly restored.
What should I do for a bunche of external disks (some of our servers
have >100 disks), that will also be 'discovered' by VxVM 4.0 and stored
in its configuration as disks of type "auto:none" ?
Is there any method in VxVM 4.0 to make the discovery of new disks store
them in the configuration as type "sliced"?
TIA
Rob
**** DISCLAIMER ****
http://www.belgacom.be/maildisclaimer
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
**** DISCLAIMER ****
http://www.belgacom.be/maildisclaimer
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:30:06 EDT