- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- lolck disk problem
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
Discussions
Discussions
Forums
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
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
тАО05-06-2009 11:04 AM
тАО05-06-2009 11:04 AM
lolck disk problem
How can I find out whai is going on - Thank you.
Trehe is log file:
May 6 15:25:01 opera2 cmcld[25936]: Obtaining Cluster Lock
May 6 15:25:01 opera2 cmdisklockd[25959]: Obtaining cluster lock device /dev/sdi1
May 6 15:25:01 opera2 cmdisklockd[25959]: Unable to obtain the lock!
May 6 15:25:01 opera2 cmcld[25936]: Attempting to form a new cluster
May 6 15:25:01 opera2 cmcld[25936]: Beginning standard election
May 6 15:25:07 opera2 cmcld[25936]: Obtaining Cluster Lock
May 6 15:25:07 opera2 cmdisklockd[25959]: Obtaining cluster lock device /dev/sdi1
May 6 15:25:07 opera2 cmdisklockd[25959]: Unable to obtain the lock!
May 6 15:25:07 opera2 cmcld[25936]: Attempting to form a new cluster
May 6 15:25:07 opera2 cmcld[25936]: Beginning standard election
May 6 15:25:12 opera2 cmcld[25936]: Obtaining Cluster Lock
May 6 15:25:12 opera2 cmdisklockd[25959]: Obtaining cluster lock device /dev/sdi1
May 6 15:25:12 opera2 cmdisklockd[25959]: Unable to obtain the lock!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-06-2009 12:51 PM
тАО05-06-2009 12:51 PM
Re: lolck disk problem
Is /dev/sdi1 *really* your lock disk device *now*? It certainly was back when you originally set up ServiceGuard, but that does not say anything about the current situation.
Please run "fdisk -l /dev/sdi" to verify that the LUN actually contains the lock partition. If it doesn't, you'll need to change your cluster ASCII file to point to the lock LUN using some persistent device name, and re-apply the cluster configuration.
I'm not very familiar with SLES, but Google tells me SLES10 has dm-multipath just like RHEL 4 and newer. Apparently the name of the necessary package is "multipath-tools". Make sure it is installed.
Then run "multipathd -v2" to initialize the multipath system, then "multipath -l" to see the mapping between the multipath device names and the regular /dev/sd* devices. Make sure "multipathd" gets started automatically at boot and start it now if necessary: it is responsible for updating the multipath mappings automatically.
The multipath device name for your lock disk will be something like "/dev/mapper/
If you don't want to use multipathing for some reason, check the /dev/disk/by-* directories: in Linux distributions with modern udev, these will offer various ways to identify your disk devices in a persistent manner.
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-06-2009 06:58 PM
тАО05-06-2009 06:58 PM
Re: lolck disk problem
Also, you didn't say whether this ever worked or not. Depending on the EVA make sure your FW is up-to-date. Some of the older EVAs were active passive devices that could possibly cause this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-06-2009 10:25 PM
тАО05-06-2009 10:25 PM
Re: lolck disk problem
cluster conf file is:
NODE_NAME opera2
NETWORK_INTERFACE bond0
STATIONARY_IP 192.168.99.107
NETWORK_INTERFACE bond1
HEARTBEAT_IP 192.168.240.2
# CLUSTER_LOCK_LUN /dev/sdi1
CLUSTER_LOCK_LUN /dev/mapper/3600508b40006836800017000010e0000-part1
opera2:/edi # cmcheckconf -v -C file1
Begin cluster verification...
Checking cluster file: file1
Value specified for CLUSTER_LOCK_LUN at line 104 is too long. Its length should not exceed 39 charaters
cmcheckconf: Error found in cluster file: file1.
opera2:/edi #
Lock LUN from EVA is 9:
opera1:/dev/mapper # multipath -l
3600508b40006836800017000010e0000 dm-18 HP,HSV200
[size=2.0G][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=-2][active]
\_ 1:0:1:9 sdcf 69:48 [active][undef]
\_ 0:0:1:9 sdah 66:16 [active][undef]
\_ round-robin 0 [prio=-2][enabled]
\_ 1:0:0:9 sdbg 67:160 [active][undef]
\_ 0:0:0:9 sdi 8:128 [active][undef]
opera2:/etc/init.d # multipath -l
3600508b40006836800017000010e0000 dm-18 HP,HSV200
[size=2.0G][features=1 queue_if_no_path][hwhandler=0]
\_ round-robin 0 [prio=-2][active]
\_ 1:0:1:9 sdcf 69:48 [active][undef]
\_ 0:0:0:9 sdi 8:128 [active][undef]
\_ round-robin 0 [prio=-2][enabled]
\_ 1:0:0:9 sdbg 67:160 [active][undef]
\_ 0:0:1:9 sdah 66:16 [active][undef]
opera1:/dev/mapper # dmsetup ls | grep 10e
3600508b40006836800017000010e0000 (253, 18)
3600508b40006836800017000010e0000-part1 (253, 37)
opera1:/dev/mapper #
opera2:/etc/init.d # dmsetup ls | grep 10e
3600508b40006836800017000010e0000 (253, 18)
3600508b40006836800017000010e0000-part1 (253, 39)
opera2:/etc/init.d #
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-07-2009 11:03 AM
тАО05-07-2009 11:03 AM
Re: lolck disk problem
it needs 4 minutes to reconfigure...
Perhaps I missing sometething - or there is bug...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-16-2015 11:11 AM
тАО01-16-2015 11:11 AM
Re: lolck disk problem
Somebody coded CLUSTER_LOCK_LUN checks wrong within cmcheckconf, it can't take standard mapper names (too long).
SO, my LOCK_LUN is /dev/mapper/3600blah-blah0000_part1 . I put in a rename at the top of 'start' case within /etc/init.d/cmcluster script as such :
/sbin/dmsetup rename /dev/mapper/3600blah-blah0000 CLUDISK 2>/dev/null
/sbin/dmsetup rename /dev/mapper/3600blah-blah0000_part1 CLUDISK_part1 2>/dev/null
NOTE: you MUST have underscore ".. _part1" , the err redirect because it may already exist
And used it in clu conf file:
CLUSTER_LOCK_LUN /dev/mapper/CLUDISK_part1
This is much easier than tweaking udev stuff which I first started to look at. You must REALLY do the above so your disk is serviced via multipathing. Otherwise your clu is hostage to just one SAN path to LOCK disk.
KEYWORDS:
Serviceguard for Linux SAPeSG Service Guard SuSE
Value specified for CLUSTER_LOCK_LUN at line is too long. Its length should not exceed characters