- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Service Guard Linux Lock Disk issue
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
12-08-2009 11:47 PM
12-08-2009 11:47 PM
Service Guard Linux Lock Disk issue
An administrator at a client has added another LUN to their SAN (a Clarion I think) and presented it to their Service Guard Linux hosts. Having rebooted the one node the disk lettering has changed so the lock disk - and just about every other disk - is now different on this node. They are getting a "Cannot reach lock device" errors on that node.
I'm sure the solution is pretty obvious, maybe I'm a few cups of coffee short of a good morning, but I can't figure it out.
Some help would be appreciated. Also any ideas on preventing this in future.
The techie stuff:
SGLX A.11.18
Redhat 4u7
HP P Series blades
Thanks in advance.
Andrew Y
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2009 12:24 AM
12-09-2009 12:24 AM
Re: Service Guard Linux Lock Disk issue
To prevent this problem in future, you may want to refer this
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=120&prodSeriesId=376220&prodTypeId=15351&objectID=c01538162
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2009 02:47 AM
12-09-2009 02:47 AM
Re: Service Guard Linux Lock Disk issue
In Linux, it is not necessary to export & import VGs - simply running "vgscan" will re-detect the VGs.
You should use something that provides persistent names for your disk devices. There are many alternatives for that: if you use LVM, it handles this automatically. But for the lock disk, you may need a different solution.
If you don't use LVM but have multiple paths to your SAN disks, some multipath solutions will also provide persistent naming (dm-multipath certainly does it).
If you use plain /dev/sd* devices, you should write some udev rules to assign persistent names for your devices.
Please see this document about using udev with Serviceguard for Linux:
http://docs.hp.com/en/8859/udev_sglinuxconfig.pdf
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2009 09:43 AM
12-09-2009 09:43 AM
Re: Service Guard Linux Lock Disk issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2009 09:52 AM
12-09-2009 09:52 AM
Re: Service Guard Linux Lock Disk issue
http://docs.hp.com/en/8859/udev_sglinuxconfig.pdf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-09-2009 08:42 PM
12-09-2009 08:42 PM
Re: Service Guard Linux Lock Disk issue
I don't remember the exact functions of the drivers with different versions of the FC drivers, but both have had persistent naming as a function (side effect) of their multipath. So if you are using multipath (and you should) then there may be a driver configuration problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2009 02:36 AM
12-17-2009 02:36 AM
Re: Service Guard Linux Lock Disk issue
Thanks for the advice.
I have tried to do as suggested but with no luck.
The /sbin/scsi_id command fails with errors when querying the disk. I suspect this is because the EMC DMX disk array is blacklisted by the scsi_id system as default. However if I run the scsi_id command with the -g -s options to get the ID I get the following:
SEMC SYMMETRIX 751545487000
I am open to suggestions on what to do.
Regards
Andrew Y