- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: VG not getting activated
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
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
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
08-11-2019 09:21 AM
08-11-2019 09:21 AM
VG not getting activated
:root>vgchange -a y /dev/vgdb2dump
vgchange: Activation mode requested for the volume group "/dev/vgdb2dump" conflicts with configured mode.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-11-2019 05:57 PM
08-11-2019 05:57 PM
Re: VG not getting activated
This system seems to be part of a Service Guard cluster.
Use: vgchange -a e /dev/vgdb2dump
If you need to remove this disk from the cluster, vgchange -c n /dev/vgdb2dump
then use vgchange -a y /dev/vgdb2dump
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-12-2019 12:47 AM
08-12-2019 12:47 AM
Re: VG not getting activated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-12-2019 01:20 AM
08-12-2019 01:20 AM
Re: VG not getting activated
how i can add it again to cluster
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-12-2019 07:02 AM
08-12-2019 07:02 AM
Re: VG not getting activated
You said that the VG was activated. What hapens when you use the mount command for the LVOLs?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2019 12:25 AM
08-13-2019 12:25 AM
Re: VG not getting activated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2019 08:44 AM
08-13-2019 08:44 AM
Re: VG not getting activated
I'm confused. What happened when you used the mount command?
The vgdisplay for vg02 seems to be fine, which means that the VG has been activated.
Based on the vgdisplay you posted, the physical extents used are 3,353 and each extent is 256 MB.
So for this listing, the VG is 858,368 MB.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2019 12:05 AM
08-14-2019 12:05 AM
Re: VG not getting activated
For vg case cluster was down that's why i am not able to check it.
Thanks for helping me in space calculation.
Can you please help me to find out the how much space is utilized .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2019 06:39 AM - edited 08-14-2019 06:39 AM
08-14-2019 06:39 AM - edited 08-14-2019 06:39 AM
Re: VG not getting activated
The space allocated to lvols is founnd in the vgdisplay output:
VG Name /dev/vg02
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 6
Open LV 12
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 3353
VGDA 2 PE
Size (Mbytes) 256
Total PE 3353
Alloc PE 3348
Free PE 5
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 13412g
VG Max Extents 53648
This VG has 3,353 extents with 3,348 allocated to LVOLs.
3,348*256=857,088 MB
If you are asking how much space is utilized by each LV, use these commands:
# mount -a
# bdf
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2019 10:55 PM
08-18-2019 10:55 PM
Re: VG not getting activated
I have bdf o/p like this and i want to increase size of /var how can i increase it.
:root>bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 5242880 842328 4366272 16% /
/dev/vg00/lvol1 2097152 478856 1605800 23% /stand
/dev/vg00/lvol8 41943040 40450488 1481016 96% /var
/dev/vg00/lvol7 15728640 3477096 12155912 22% /usr
/dev/vg00/lvol6 10485760 689616 9719760 7% /tmp
/dev/vg00/lvol5 16777216 7964976 8744040 48% /opt
/dev/vg00/lvol4 5242880 20984 5181104 0% /home