Tru64 V5.0A / TruCluster V5.0A (+patches)
I have been happily migrating LSM volumes from one system to a *cluster*
but have become stuck on one particular volume whereby, upon boot-up, LSM
rejects an LSM disk with;
starting LSM in boot mode
lsm:vold: WARNING: Disk dskX: Disk rejected as clone
Switching on debug mode on 'vold' it appears the failure is reported after
'devintf_check_wwid', however the WWIDs are clearly distinct and have
obviously been working flawlessly prior to the transition. After the boot
LSM claims the 'cloned' disk has 'aliased partitions'. There is only one
hardware path to the disk concerned and the pub/priv paths are correct.
Any ideas out there ?
John P.
Received on Tue Sep 05 2000 - 15:50:18 NZST