From: Stuart Walker (stuartw@sydney.net)
Date: Thu Feb 20 2003 - 03:30:29 EST
Hi there.
We have a 4.0F Tru64 system, running TruCluster 1.6. For various reasons
(don't ask...), we need to "move" various drd device from one cluster service
to another, keeping the same drd device number. Now, I know that asemgr
automatically allocates a drd device when you "a) Add LSM volume or physical
disk". Using an example:
Service "X" : /dev/rdrd/drd1001 -> /dev/rrz1b
/dev/rdrd/drd1002 -> /dev/rrz1d
/dev/rdrd/drd1003 -> /dev/rrz2b
Service "Y" : /dev/rdrd/drd1004 -> /dev/rrz2d
/dev/rdrd/drd1005 -> /dev/rrz2e
/dev/rdrd/drd1006 -> /dev/rrz2f
We want to END UP with:
Service "X" : /dev/rdrd/drd1001 -> /dev/rrz1b
/dev/rdrd/drd1002 -> /dev/rrz1d
/dev/rdrd/drd1003 -> /dev/rrz2b
/dev/rdrd/drd1004 -> /dev/rrz2d
/dev/rdrd/drd1005 -> /dev/rrz2e
Service "Y" : /dev/rdrd/drd1006 -> /dev/rrz2f
Naturally, I'd have to be careful of the order in which I deleted and created
the devices in order to keep the drd -> disk-device relationship, but you get
the idea.
My suspicions are, however, that when a device is deleted, its "drd number"
is not necessarily re-used immediately. i.e. I have no idea what
algorithm/method asemgr uses when allocating these drd devices.
Anyone got any ideas?
The reaons for this are a little perverse, but necessary.
Regards,
Stuart
E-mail: StuartW@BECons.com.au
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:08 EDT