- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- dev name of Cluster Lock Disk changes
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
06-08-2006 01:31 AM
06-08-2006 01:31 AM
dev name of Cluster Lock Disk changes
I'm running a cluster of two DL380 Servers. The shared storage consists of two MSA1000 storages which are connected to each server. I'd like to build a RAID1 with these two storages. And I'd like one of the storage to hold the Cluster Lock Lun (CLL). Each storage has its own controller on the server.
The Software I'm using is SLES9 SP3 and MCSGLX 11.16.05.
The problem:
If the servers start the LUNs of the storage are numbered from /dev/sda to /dev/sdo. I've set /dev/sda1 to be the Cluster-Lock-Lun. This worked actually fine. Now I've move one server into another room (I've lengthened the connections by fibre channel). As the servers restarted the partition that appeared to be /dev/sda is now /dev/sdh. I've used scsidev to put an alias on this disk which worked fine. The name of this CLL is now /dev/scsi/locklun and I can verify that the disk which can be accessed as /dev/sda1 and /dev/scsi/locklun on one node is as well /dev/sdh1 and /dev/scsi/locklun on the other node. But if I try to use this name /dev/scsi/locklun an error message appears:
Begin cluster verification...
Error: Cannot get disk partition for device /dev/scsi/locklunError: Invalid data for cluster lock LUN configuration
cmcheckconf : Unable to verify cluster file: /opt/cmcluster/conf/cmclconfig.ascii.
Has anybody expirienced this phanomenon ?
Is there another way to change the way the disks are numbered ?
How can I make SG to use the alias of the CLL ?
gromit:~ # sfdisk -s
/dev/sda: 10485600
/dev/sdb: 10485600
/dev/sdc: 10485600
/dev/sdd: 10485600
/dev/sde: 10485600
/dev/sdf: 10485600
/dev/sdg: 7862160
/dev/sdh: 16320 <-- CLL
/dev/sdi: 10485600
/dev/sdj: 10485600
/dev/sdk: 10485600
/dev/sdl: 10485600
/dev/sdm: 10485600
/dev/sdn: 10485600
/dev/sdo: 7862160
gromit:~ # sfdisk -s /dev/sdh1
16304
gromit:~ # sfdisk -s /dev/scsi/locklun
16304
wallace:~ # sfdisk -s
/dev/sda: 16320 <-- CLL
/dev/sdb: 10485600
/dev/sdc: 10485600
/dev/sdd: 10485600
/dev/sde: 10485600
/dev/sdf: 10485600
/dev/sdg: 10485600
/dev/sdh: 7862160
/dev/sdi: 10485600
/dev/sdj: 10485600
/dev/sdk: 10485600
/dev/sdl: 10485600
/dev/sdm: 10485600
/dev/sdn: 10485600
/dev/sdo: 7862160
wallace:~ # sfdisk -s /dev/sda1
16304
wallace:~ # sfdisk -s /dev/scsi/locklun
16304
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-08-2006 02:44 AM
06-08-2006 02:44 AM
Re: dev name of Cluster Lock Disk changes
When the device changes, you need to cmcheckconf and then cmapplyconf
Have you done this since the disk configuration change?
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
06-08-2006 03:17 PM
06-08-2006 03:17 PM
Re: dev name of Cluster Lock Disk changes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-08-2006 05:42 PM
06-08-2006 05:42 PM
Re: dev name of Cluster Lock Disk changes
the error message that's in the text is the output of the cmcheckconf command.
I'll try the udev method. I'll let you know the results.
Thanks & Regards
Matthias
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2006 09:39 PM
06-11-2006 09:39 PM
Re: dev name of Cluster Lock Disk changes
the assignement of a disk by udev solved the problem.
I have installed udev on both servers and setup the boot script for it. The exercise is to modify the file
/etc/udev/udev.rules.
I needed to add the line
BUS=="scsi", SYSFS{vendor}=="COMPAQ ", SYSFS{model}=="MSA1000 VOLUME ", SYSFS{size}=="32608", NAME="sdz%n\
"
to the mentioned file on all cluster nodes. The used CLL is /dev/sdz1.
Thanks & regards
Matthias