Thanks go to Jason Orendorf for pointing out that LSM is cluster aware,
therefore each node saves identical configurations, so only cluster alias is
needed. I'll amend the cron jobs so as only one runs at a time. In this way
we should get at least 1 valid volsave per day regardless of whether one
member is down or not.
Orginial Question:
Hello all,
I've just upgraded a two GS320 member cluster from v5.1 to v5.1A PK3.
Upgrade went suprisingly well and I've experienced no problems except for
one thing. We daily via cron execute a volsave command to save all the LSM
configuration on the machine. The command gets executed on both nodes of the
cluster. Under 5.1 volsave command saves to a directory such as
/usr/var/lsm/db/LSM.20030129182500.hostname. However the behaviour seems
different under 5.1A and it save it under
/usr/var/lsm/db/LSM.20030129182500.clusteralias. Which means that each node
in the cluster is trying to write to the same directory. I've checked the
man page but I can't see a way I can specify to use hostname rather than
cluster alias. Has anyone else experienced this or know how to resolve the
problem.
Robert Mulley
System Administrator
The Travel Corporation Pty Ltd
Travel House
35 Grafton Street
Woollahra NSW 2025
(02) 9028 5585
Received on Thu Jan 30 2003 - 22:00:59 NZDT