Sorry for the delayed summary, buy my servers are ganging up against me. Here is my original post:
Ok...it's been a bad week. I have yet another question (while still trying to figure out my other problems). This has to do with LSM in Tru64 5.1. Our system is a bit odd--let me explain. We have a whole bunch of disks on an HSG80 controller--and 4 systems connected to the HSG80s (two running 5.0a, one running 4.0f, and the newest one runing 5.1). The controllers are set to allow ALL hosts to access any of the disks. We do not use any clustering at all. These disks contain a bunch of Informix databases. We have 6 production images so we use LSM to make a group for each image (ie image_01 etc). On any of the non-5.1 systems I can do whatever I want to the LSM configuration even if another system is using the disks at the time--nothing goes wrong as long as two systems aren't both trying to write to the disks at the same time. Anyway...I was just configuring the new 5.1 system with the LSM, and I enter the following:
voldisksetup -i dsk12 nlog=2 nconfig=2 privlen=1024
voldisksetup -i dsk23 nlog=2 nconfig=2 privlen=1024
all of the other systems will be more than happy to do this, even if the disks are in use by another system...but the 5.1 system says:
dsk12 is marked in use for LSMpriv in the disklabel.
If you continue with the operation you can
possibly destroy existing data.
CONTINUE ? [y/n] n
So my question is: why doesn't this work with a 5.1 system? We do it VERY often with the other systems with no problems. does anyone know of a way around this? I've got a call into Compaq, but they hate how we set up our system (even though it worked extremely well until now) and always tell us it's not a supported configuration. Anyway...hope this makes some sort of sense...
########################
And here is my summary:
After receiving quite a few responses, and a few phone calls with compaq, we have somewhat solved our problem. We received that error message because LSM had already discovered the disks, and added them to its "voldisk list" output. They were online, but not initialized or setup at all. So I just had to do a "voldg rm dsk12" for all of the disks.
I am happy I asked this question though, because it turns out that LSM in 5.1 is all-new, and the metadata has changed. It is not a problem when you move a disk from earlier versions of LSM to the new version (they apparently get converted automatically), but being they get converted, you cannot put these disks back on a system with an ealier version of LSM. Not too big a deal being we will be upgrading all of our servers to 5.1 in the next few weeks. Thanks soo much to all who have replied.
Jonathan Williams
UNIX Systems Administrator
The Shubert Organization, Inc.
Received on Wed Aug 08 2001 - 12:35:40 NZST