Hello Managers,
Tru64 v5.1A PK1 - ES40 connected to two HSG80 controllers.
I deported a disk group from a running cluster. Tried to import the group on a stand alone machine using the same disks on the HSG80 controllers. The cluster which originally had the disks is completely shut down.
Before the import I completely reinitialized LSM with a new rootdg then ran
Voldg -C -o private import hdbdg
The group spans 44 hsg80 disk partitions (22 on each HSG80).
The disk group was setup to have 8 config/log copies at any given time and were distributed evenly between both hsg80 controllers and disks.
Basically the import fails every time displaying:
Lsm:voldg: ERROR: Disk group hdbdg: import failed: No valid log copies in disk group
Lsm:voldg: ERROR: hdbdg is not configured as private; use "-o private" to import hdbdg.
Well I did use -o private. I tried it without -o private and got the same message about needing to use -o private both times.
When examining the LSMpriv partitions on each of the disks in the disk group with /usr/lib/lsm/bin/volprivutil I found I still had 7 of my config/log disks.
However using the dumplog option it displays the following on every disk in the group:
Lsm:volprivutil: ERROR: log block 0: Log block invalid
The log block number increases by 1 until it reaches 127 when it quits.
On a disk with a good log in another group I get this:
BLOCK 0: KLOG 0 : COMMIT tid=0.1034
The disk group was clean when it was deported so I would think there should be away around this problem. I just haven't found it yet. It would seem that if I would rewrite the log to be in a sane state everything would be okay.
Any idea/help/etc. would be very much welcome and appreciated!
Many thanks for your time,
Chris
Received on Wed Mar 06 2002 - 23:34:41 NZDT