- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- VG not mounting custom_vg_activation() is set...
Operating System - HP-UX
1748204
Members
3080
Online
108759
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
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО09-13-2007 06:11 PM
тАО09-13-2007 06:11 PM
I am having an issue with a VG not mounting during a reboot. The needs to manually be activated and mounted...
Here is my LVMRC file.
I have a vg that will not mount.
I have set AUTO_VG_ACTIVATE=0
and aslo have this setting for
custom_vg_activation()
{
/sbin/vgchange -a y -s vgora
parallel_vg_sync "/dev/vgora"
return 0
}
Does anything look wrong with this setting?
Here is my LVMRC file.
I have a vg that will not mount.
I have set AUTO_VG_ACTIVATE=0
and aslo have this setting for
custom_vg_activation()
{
/sbin/vgchange -a y -s vgora
parallel_vg_sync "/dev/vgora"
return 0
}
Does anything look wrong with this setting?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2007 06:28 PM
тАО09-13-2007 06:28 PM
Solution
If the VG is part of the cluster, then "-a y" won't work. This must be "-a e" or even "-a s" in this case. Have a look into the log for a related message.
BTW, why you use "-s"?
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
BTW, why you use "-s"?
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2007 07:04 PM
тАО09-13-2007 07:04 PM
Re: VG not mounting custom_vg_activation() is set...
Well rc.log just shows the command
minus the -s incidently...
As far why we are using the -s I cant say. I dont see any harm in it though. I think this command was chosen as it was documetend that way. I will experiment with your suggestions.
Also is there a another location I can look for more detail on the output from this file?
minus the -s incidently...
As far why we are using the -s I cant say. I dont see any harm in it though. I think this command was chosen as it was documetend that way. I will experiment with your suggestions.
Also is there a another location I can look for more detail on the output from this file?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2007 11:41 PM
тАО09-13-2007 11:41 PM
Re: VG not mounting custom_vg_activation() is set...
Hi,
This is part of the /etc/lvmrc of the adoptive node of my cluster and it activates the following VGs during reboot. These VGs are NOT part of a cluster's package(s).
------------------------------------
custom_vg_activation()
{
# e.g. /sbin/vgchange -a y -s
# parallel_vg_sync "/dev/vg00 /dev/vg01"
# parallel_vg_sync "/dev/vg02 /dev/vg03"
/sbin/vgchange -a y -s /dev/vg00
/sbin/vgchange -a y -s /dev/vg_RS2_01
/sbin/vgchange -a y -s /dev/vg_RT2_01
/sbin/vgchange -a y -s /dev/vg_RT2_02
/sbin/vgchange -a y -s /dev/vg_RT2_03
/sbin/vgchange -a y -s /dev/vg_RT1_APP
/sbin/vgchange -a y -s /dev/vg_PT101
/sbin/vgchange -a y -s /dev/vg_INTERFACE
/sbin/vgchange -a y -s /dev/vg_RT101
/sbin/vgchange -a y -s /dev/vg_RT102
/sbin/vgchange -a y -s /dev/vg_RD101
/sbin/vgchange -a y -s /dev/vg_RD102
parallel_vg_sync "/dev/vg00 /dev/vg_RS2_01 /dev/vg_RT2_01 /dev/vg_RT2_02 /dev/vg_RT2_03 \
/dev/vg_RT1_APP /dev/vg_PT101 /dev/vg_INTERFACE /dev/vg_RT101 /dev/vg_RT102 \
/dev/vg_RD101 /dev/vg_RD102"
return 0
}
-----------------------------------------
If the server in question is part of the node , it is recommended to set AUTO_VG_ACTIVATE to 0 and let the ServiceGuard package control file to activate the package volume group (which is usually vgchange -a e).
Regards,
Charlie
This is part of the /etc/lvmrc of the adoptive node of my cluster and it activates the following VGs during reboot. These VGs are NOT part of a cluster's package(s).
------------------------------------
custom_vg_activation()
{
# e.g. /sbin/vgchange -a y -s
# parallel_vg_sync "/dev/vg00 /dev/vg01"
# parallel_vg_sync "/dev/vg02 /dev/vg03"
/sbin/vgchange -a y -s /dev/vg00
/sbin/vgchange -a y -s /dev/vg_RS2_01
/sbin/vgchange -a y -s /dev/vg_RT2_01
/sbin/vgchange -a y -s /dev/vg_RT2_02
/sbin/vgchange -a y -s /dev/vg_RT2_03
/sbin/vgchange -a y -s /dev/vg_RT1_APP
/sbin/vgchange -a y -s /dev/vg_PT101
/sbin/vgchange -a y -s /dev/vg_INTERFACE
/sbin/vgchange -a y -s /dev/vg_RT101
/sbin/vgchange -a y -s /dev/vg_RT102
/sbin/vgchange -a y -s /dev/vg_RD101
/sbin/vgchange -a y -s /dev/vg_RD102
parallel_vg_sync "/dev/vg00 /dev/vg_RS2_01 /dev/vg_RT2_01 /dev/vg_RT2_02 /dev/vg_RT2_03 \
/dev/vg_RT1_APP /dev/vg_PT101 /dev/vg_INTERFACE /dev/vg_RT101 /dev/vg_RT102 \
/dev/vg_RD101 /dev/vg_RD102"
return 0
}
-----------------------------------------
If the server in question is part of the node , it is recommended to set AUTO_VG_ACTIVATE to 0 and let the ServiceGuard package control file to activate the package volume group (which is usually vgchange -a e).
Regards,
Charlie
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP