- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Lun Lock on redhat/SuSe
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
тАО04-06-2006 09:28 PM
тАО04-06-2006 09:28 PM
Lun Lock on redhat/SuSe
May I know how to fix the scsi disk path on linux?
Currently my Lun Lock is /dev/sda=150Mb ,after i create new lun .The Lun Lock become /dev/sdb .HOw could I fix /dev/sda=150Mb as permanent .
Thanks
LeongKO
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-07-2006 01:04 AM
тАО04-07-2006 01:04 AM
Re: Lun Lock on redhat/SuSe
LABEL=mydata /mydata ext3 defaults 0 0
For SUSE, see:
http://www-uxsup.csx.cam.ac.uk/pub/doc/suse/sles9/adminguide-sles9/ch03s08.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2006 07:02 PM
тАО04-09-2006 07:02 PM
Re: Lun Lock on redhat/SuSe
Do i need to set the lun lock path on the cluster scripts same as label ?
second ,
The Lun Lock can i mount on both server ?
Thanks
LeongKO
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-10-2006 01:16 AM
тАО04-10-2006 01:16 AM
Re: Lun Lock on redhat/SuSe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-10-2006 03:46 AM
тАО04-10-2006 03:46 AM
Re: Lun Lock on redhat/SuSe
I am using HP Linux serviceguard .
The cluster file .
LunLock=/dev/sda1 ,should i change to
LunLock=/mydata
Thanks
LeongKO
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-10-2006 04:34 AM
тАО04-10-2006 04:34 AM
Re: Lun Lock on redhat/SuSe
devlabel add ├в s /dev/my_stable_name ├в d /dev/sda
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-10-2006 10:44 AM
тАО04-10-2006 10:44 AM
Re: Lun Lock on redhat/SuSe
The devlabel software attempts to address the device naming issue in a different manner than file system labels. The devlabel software is run by Red Hat Enterprise Linux whenever the system reboots (and whenever hotpluggable devices are inserted or removed).
When devlabel runs, it reads its configuration file (/etc/sysconfig/devlabel) to obtain the list of devices for which it is responsible. For each device on the list, there is a symbolic link (chosen by the system administrator) and the device's UUID (Universal Unique IDentifier).
The devlabel command makes sure the symbolic link always refers to the originally-specified device ├в even if that device's name has changed. In this way, a system administrator can configure a system to refer to /dev/projdisk instead of /dev/sda12, for example.
Because the UUID is obtained directly from the device, devlabel must only search the system for the matching UUID and update the symbolic link appropriately.
# devlabel add -s /dev/my_stable_disk_name -d /dev/sda
So, in your configuration file, you will specify:
/dev/my_stable_disk_name
Instead of /dev/sda.