HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Failover node with same name file system
Operating System - HP-UX
1833807
Members
3991
Online
110063
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
02-28-2007 05:20 PM
02-28-2007 05:20 PM
Failover node with same name file system
OS: HPUX
ServiceGuard: 11.16
2 Nodes: hp-node1, hp-node2
The primary node: hp-node1
The problem: hp-node2 run 3 file system with de same name de file system cluster configuration, The scripts the package no umount the file system and the package fail.
When configure the umount file system and desactive de volumen group first?
Regards
Rene
ServiceGuard: 11.16
2 Nodes: hp-node1, hp-node2
The primary node: hp-node1
The problem: hp-node2 run 3 file system with de same name de file system cluster configuration, The scripts the package no umount the file system and the package fail.
When configure the umount file system and desactive de volumen group first?
Regards
Rene
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2007 01:45 AM
03-01-2007 01:45 AM
Re: Failover node with same name file system
Rene, I'm not exactly sure what you mean but I'll take a stab at it.
It appears that you have 3 file systems mounted on hp-node2 that you want to be unmounted when the SG package is started on that node, because the package uses the same mount directory names. If this is correct, then the standard package control script does not have this capability. You would have to customize the script to check the hostname, and if it is hp-node2, 'fuser -ku' the file systems and then unmount them before the package control script attempts to mount file systems.
Customizing the script with a new functions is not supported by Serviceguard at this time, though it can be done. If you were to do it, you must incorporate a new test_return case for the function
It appears that you have 3 file systems mounted on hp-node2 that you want to be unmounted when the SG package is started on that node, because the package uses the same mount directory names. If this is correct, then the standard package control script does not have this capability. You would have to customize the script to check the hostname, and if it is hp-node2, 'fuser -ku' the file systems and then unmount them before the package control script attempts to mount file systems.
Customizing the script with a new functions is not supported by Serviceguard at this time, though it can be done. If you were to do it, you must incorporate a new test_return case for the function
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