HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Could I change FIRST_CLUSTER_LOCK_PV?
Operating System - HP-UX
1833881
Members
1599
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2003 09:08 PM
10-19-2003 09:08 PM
Hi,
I have this error in the syslog
Oct 20 10:37:52 hp9ges02 cmcld: WARNING: Cluster lock disk /dev/dsk/c4t1d0 has failed: I/O error
Oct 20 10:37:52 hp9ges02 cmcld: Until it is fixed, a single failure could
Oct 20 10:37:52 hp9ges02 cmcld: cause all nodes in the cluster to crash
This disk is the FIRST_CLUSTER_LOCK_PV, and now I haven't got this disk.... Could I change to another disk?, what I have to do?
Thanks!!
Carmen.
NODE_NAME hp9ges02
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.32.54.2
NETWORK_INTERFACE lan1
STATIONARY_IP 10.32.13.3
NETWORK_INTERFACE lan2
HEARTBEAT_IP 192.168.233.10
FIRST_CLUSTER_LOCK_PV /dev/dsk/c4t1d0
I have this error in the syslog
Oct 20 10:37:52 hp9ges02 cmcld: WARNING: Cluster lock disk /dev/dsk/c4t1d0 has failed: I/O error
Oct 20 10:37:52 hp9ges02 cmcld: Until it is fixed, a single failure could
Oct 20 10:37:52 hp9ges02 cmcld: cause all nodes in the cluster to crash
This disk is the FIRST_CLUSTER_LOCK_PV, and now I haven't got this disk.... Could I change to another disk?, what I have to do?
Thanks!!
Carmen.
NODE_NAME hp9ges02
NETWORK_INTERFACE lan0
HEARTBEAT_IP 10.32.54.2
NETWORK_INTERFACE lan1
STATIONARY_IP 10.32.13.3
NETWORK_INTERFACE lan2
HEARTBEAT_IP 192.168.233.10
FIRST_CLUSTER_LOCK_PV /dev/dsk/c4t1d0
Users are not too bad ;-)
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2003 09:12 PM
10-19-2003 09:12 PM
Solution
Here is a cookbook:
How to initialize the cluster lock disk(s) using cmapplyconf:
â ¢ Halt the entire cluster.
# cmhaltcl -f
â ¢ Perform the following command from all nodes in the cluster to remove the cluster
flag from cluster lock VG(s).
# vgchange -c n /dev/vgxxx
â ¢ Activate cluster lock VG(s) on one node only:
# vgchange -a y /dev/vgxxx
â ¢ Perform cmapplyconf on the node where you activated the cluster lock VG(s). The
cluster flag is added back to the VG automatically.
# cmapplyconf -C ........
â ¢ Perform vgcfgbackup to backup the cluster lock information:
# vgcfgbackup /dev/vgxxx
â ¢ Deactivate cluster lock VG(s):
# vgchange -a n /dev/vgxxx
â ¢ Run vgcfgbackup on all other cluster nodes also:
# vgchange -a r vgxxx
# vgcfgbackup vgxxx
# vgchange -a n vgxxx
â ¢ Restart the cluster:
# c
How to initialize the cluster lock disk(s) using cmapplyconf:
â ¢ Halt the entire cluster.
# cmhaltcl -f
â ¢ Perform the following command from all nodes in the cluster to remove the cluster
flag from cluster lock VG(s).
# vgchange -c n /dev/vgxxx
â ¢ Activate cluster lock VG(s) on one node only:
# vgchange -a y /dev/vgxxx
â ¢ Perform cmapplyconf on the node where you activated the cluster lock VG(s). The
cluster flag is added back to the VG automatically.
# cmapplyconf -C ........
â ¢ Perform vgcfgbackup to backup the cluster lock information:
# vgcfgbackup /dev/vgxxx
â ¢ Deactivate cluster lock VG(s):
# vgchange -a n /dev/vgxxx
â ¢ Run vgcfgbackup on all other cluster nodes also:
# vgchange -a r vgxxx
# vgcfgbackup vgxxx
# vgchange -a n vgxxx
â ¢ Restart the cluster:
# c
He's a real UNIX Man, sitting in his UNIX LAN making all his UNIX plans for nobody ...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2003 09:12 PM
10-19-2003 09:12 PM
Re: Could I change FIRST_CLUSTER_LOCK_PV?
First check if the disk is OK?
(pvdisplay, diskinfo, vgdisplay)
Also use cminitlock command to check if there is anything wrong with the disk. If bad replace it with new one.
(run cminit in preview mode)
Use cminitlock to check it.
(pvdisplay, diskinfo, vgdisplay)
Also use cminitlock command to check if there is anything wrong with the disk. If bad replace it with new one.
(run cminit in preview mode)
Use cminitlock to check it.
There is no substitute to HARDWORK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-19-2003 09:33 PM
10-19-2003 09:33 PM
Re: Could I change FIRST_CLUSTER_LOCK_PV?
Thanks!,
The this doesn't exist... I don't know what happended but supposed was change to another with another path... now I have one disk c3t2d0....
I want to change it to this new.
The this doesn't exist... I don't know what happended but supposed was change to another with another path... now I have one disk c3t2d0....
I want to change it to this new.
Users are not too bad ;-)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP