- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Auto VG activation 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-29-2010 08:34 AM
12-29-2010 08:34 AM
Auto VG activation issue
In /etc/lvmrc I set:
AUTO_VG_ACTIVATE=0
and updated:
custom_vg_activation()
{
/sbin/vgchange -a y -s /dev/vg00
/sbin/vgchange -a y -s /dev/vg_cla_99
parallel_vg_sync "/dev/vg00 /dev/vg_cla_99"
return 0
}
but upon reboot vg_cla_99 is not active:
# vgdisplay vg_cla_99
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "vg_cla_99".
Am I missing something?
The other VG's activate properly when the cluster package starts.
Full /etc/lvmrc attached.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-29-2010 09:35 AM
12-29-2010 09:35 AM
Re: Auto VG activation issue
What happens if you try to activate it manually?
Does vg_cla_99 have the cluster attribute set?
Cluster VGs cannot be activated that early in the boot sequence. Cluster VGs can be activated only after Serviceguard has started and the node has successfully joined the cluster.
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-29-2010 10:00 AM
12-29-2010 10:00 AM
Re: Auto VG activation issue
The only related entry in /etc/rc.log is that the VG is not active and fails to mount the filesystems:
Mount file systems
Output from "/sbin/rc1.d/S100localmount start":
----------------------------
mountall: cannot mount /dev/vg_cla_99/var_opt_perfdata
mountall: diagnostics from mount
UX:vxfs mount: ERROR: V-3-20003: Cannot open /dev/vg_cla_99/var_opt_perfdata: No such device or address
UX:vxfs mount: ERROR: V-3-24996: Unable to get disk layout version
There is nothing regrading a boot-time activation attempt before that.
I can activate the VG manually with no problems and mount the filesystems.
The cluster attribute is not set on vg_cla_99.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-29-2010 10:04 AM
12-29-2010 10:04 AM
Re: Auto VG activation issue
UNIX because I majored in cryptology...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-29-2010 10:25 AM
12-29-2010 10:25 AM
Re: Auto VG activation issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-30-2010 06:10 AM
12-30-2010 06:10 AM
Re: Auto VG activation issue
With the help of HP support:
- vg_cla_99 is not mirrored so removed the -s
- removed the parallel_vg_sync function call
- remove the newline between the vgchange and return 0
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 /dev/vg_cla_99
return 0
}
and it worked!