HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Error with cmlocklund
Operating System - HP-UX
1833695
Members
3698
Online
110062
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
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
03-20-2009 10:06 AM
03-20-2009 10:06 AM
Error with cmlocklund
Y'ello,
I'm facing the following errors on my system after every seconds:
Mar 20 18:57:14 mysys cmlocklund[18789]: Could not open cluster lock lun /dev/raw/raw1: Device or resource busy
Mar 20 18:57:14 mysys cmlocklund[18789]: Process will abort and be restarted .
Mar 20 18:57:14 mysys cmlocklund[18789]: Error opening device /dev/raw/raw1
Mar 20 18:57:14 mysys cmcld[19691]: Service cmlocklund terminated due to an exit(1).
Mar 20 18:57:14 mysys cmlocklund[18790]: Total allocated: 540672 bytes, used: 0 bytes, unused 540672 bytes
Mar 20 18:57:14 mysys cmcld[19691]: Automatically restarted service cmlocklund for the 5171807th time after failure.
The Storage is a SUN Storage 6140 and the Cluster is Service Guard.
if anybody is aware of this issue and how to fix it , let's me know.
I'm facing the following errors on my system after every seconds:
Mar 20 18:57:14 mysys cmlocklund[18789]: Could not open cluster lock lun /dev/raw/raw1: Device or resource busy
Mar 20 18:57:14 mysys cmlocklund[18789]: Process will abort and be restarted .
Mar 20 18:57:14 mysys cmlocklund[18789]: Error opening device /dev/raw/raw1
Mar 20 18:57:14 mysys cmcld[19691]: Service cmlocklund terminated due to an exit(1).
Mar 20 18:57:14 mysys cmlocklund[18790]: Total allocated: 540672 bytes, used: 0 bytes, unused 540672 bytes
Mar 20 18:57:14 mysys cmcld[19691]: Automatically restarted service cmlocklund for the 5171807th time after failure.
The Storage is a SUN Storage 6140 and the Cluster is Service Guard.
if anybody is aware of this issue and how to fix it , let's me know.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2009 07:10 PM
03-22-2009 07:10 PM
Re: Error with cmlocklund
/dev/raw is not supported for LockLun.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2009 12:21 AM
03-23-2009 12:21 AM
Re: Error with cmlocklund
The raw driver is used on older SG releases, i.e. 11.16 to get raw access to the locklun device. I have seen this error a number of times but mostly when device mapper (dm) is used as a locklun device.
dm did not support raw access so the open fails once the device is bound to the raw device.
If this is the problem then you need to use the underlying device not a dm device.
Other possibilities are that the device is already open some other way, for example if the device is mounted you would get the same problem.
Serviceguard 11.18 does not use the raw device which has pretty much been superseded by other methods for bypassing the cache.
You do not mention the version of either Linux or Serviceguard but I would guess SG 11.16 and probably RH4? If this is the case you can upgrade to 11.18.
dm did not support raw access so the open fails once the device is bound to the raw device.
If this is the problem then you need to use the underlying device not a dm device.
Other possibilities are that the device is already open some other way, for example if the device is mounted you would get the same problem.
Serviceguard 11.18 does not use the raw device which has pretty much been superseded by other methods for bypassing the cache.
You do not mention the version of either Linux or Serviceguard but I would guess SG 11.16 and probably RH4? If this is the case you can upgrade to 11.18.
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