- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- cluster lock disk
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
08-10-2006 10:18 PM
08-10-2006 10:18 PM
Is it normal that the cluster lock disk will not be activated? I don't have any lv on it.
What do you advice?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2006 10:20 PM
08-10-2006 10:20 PM
SolutionIf you have a dedicated CL disk and VG,not activated by any package, then this would be normal
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2006 10:24 PM
08-10-2006 10:24 PM
Re: cluster lock disk
This points to a few possible issues:
1) The cluster lock disk does not get "activated" When heartbeat is lost both nodes attempt to establish a lock on it. The first node achieves it, the one second one if it tries should fail and TOC, wish is a reboot with a crash dump.
2) There will be no noticable disk activity on the cluster lock disk when a cluster uses it so dont look for a flashing green light.
3) The possible problem maybe a prolbem the the configuration on both nodes not being consistent, the binary configuration files being different or perhaps you have two heartbeats and disrupting one does not trigger any cluster change.
You need to look at /var/adm/syslog/syslog.log on both systems when testing and that will provide you some clue as to what is happening.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2006 10:26 PM
08-10-2006 10:26 PM
Re: cluster lock disk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2006 10:47 PM
08-10-2006 10:47 PM
Re: cluster lock disk
Very iteresting. I've never checked that.
http://docs.hp.com/en/B9903-90035/B9903-90035.pdf
Its a linux doc but it has a reference to the cluster lock disk and bit, and may contain the command you seek.
The way I tell the cluster lock disk has been activated is the second node going TOC on me.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2006 11:17 PM
08-10-2006 11:17 PM
Re: cluster lock disk
Not easy!
This is written in the Bad Block Relocation area of the disk (hence the reason you cannot mirror this bit).
When you start your cluster running, it polls teh configured disc from each node at start time an dthen every 60 minutes.
If the bit were NOT set, it would log the cluster lock disc as unavailable in syslog.log.