[Veritas-vx] Discovered disk names [SEC=UNCLASSIFIED]
greg.robinson at dsto.defence.gov.au
Thu Sep 2 02:47:20 CDT 2010
There are 2 ways I can think of to achieve what you want:
1. delete /etc/vx/disk.info and run vxdctl enable (don't edit it, it's
rebuilt at every boot). This will rebuild that file and set up all your
vx devices. However, this is not a guarantee that the devices will be
in order. The order will be whatever the OS has decided it is, based on
2. To try and achieve physical device discovery is in order, the only
way I can think of is to present each of the 29 disks to the cluster 1
at a time. And then run vxdctl enable after each disk discovery.
However, this still won't guarantee in order device discovery, as the
devices have already been discovered. You may need to do some funky
commands with devfsadm -C and luxadm to really get rid of the physical
devices. (Even cfgadm to remove the array entirely and start again).
Hey - you've got a cluster - just reboot -- -r after removing the
Enabling enclosure based naming won't affect anything. It may change
some existing disks names, but you will see it will be better. It will
make it easier for you to identify which array is which.
From: veritas-vx-bounces at mailman.eng.auburn.edu
[mailto:veritas-vx-bounces at mailman.eng.auburn.edu] On Behalf Of Neil
Sent: Thursday, 2 September 2010 4:42 PM
To: veritas-vx at mailman.eng.auburn.edu
Subject: [Veritas-vx] Discovered disk names
I recently vxdctl enabled to see some new Hitachi LUN's (new array to
servers too) on two servers in a VCS cluster. The disks have been JBOD
named by the look of it (Disk_0 to Disk_28) rather than enclosure named.
I believe that this may be because I had an old version of the ASL
installed. I've now updated this ASL.
Additionally, whilst the Solaris device names seem to match on the two
cluster nodes, the Disk_x names do not. This doesn't technically
but since this is a cluster I was hoping to get both nodes to look the
same for easier management. and disk identification.
So....does anyone know the easiest way to wipe out the new VX disks (not
the OS devices) so I can re-vxdctl enable and hope that the new ASL
picks the enclosure up correctly (OR can I just try and apply enclosure
based naming through vxddladm ??? and if so will this affect other,
AND if I manage that (or even if not!) is there an easy way to get the
sides to match ? It seems I can edit /etc/vx/disk.info but is that the
Veritas-vx maillist - Veritas-vx at mailman.eng.auburn.edu
IMPORTANT: This email remains the property of the Department of Defence
and is subject to the jurisdiction of section 70 of the Crimes Act 1914.
If you have received this email in error, you are requested to contact
the sender and delete the email.
More information about the Veritas-vx