Anyway, thanks for the output. It gives us:-
From the manual page for mkvg, we read:-
Quote:
When creating the default volume group type (with a maximum of 32 PVs) or the big volume group type (with a maximum of 128 PVs), there is a
limitation of 1016 physical partitions per PV. When specifying the physical partition size (-s), make sure the value is set large enough so
that 1016 physical partitions per PV limit is not violated. For example, a partition size of at least 16 MB would be needed to create a volume
group with a 10 GB disk. Using a factor size (-t) of 2, a smaller partition size of 8 MB can be used. If a factor value is specified, the
maximum number of PVs that can be included in the volume group is MaxPVs/factor.
I think that you have reached this limit. Have a calculate to see if you agree. When creating the VG, the PP size has been set larger, possibly automatically for a 3Tb volume group.
Read the manual page for chvg and see if you might get away with chvg -G but read the manual first to see if it applies safely to you.
You may need to build a new volume group and add more logical volumes in there. Our main Oracle database has 12 volume groups with around 30 logical volumes in each. What do you need to add the extra disk for? There is space to grow LVs in your current VG - although it's only about about 3G which is pretty small for this VG I suppose.
How can i restart the console getty without rebooting the system on HPUX 11.0
Normally it will be stated by ps -ef | grep getty
console 0:00 /usr/sbin/getty console console
many thanx (4 Replies)
WARNING - /usr/sbin/fsck not found. Most likely the mount of
/usr failed or the /usr filesystem is badly
damaged. The system is being halted.
Either re-install the system of boot with -b
option in an attempt to recover
Anyone help me on restoring this without having to reinstall. it is a... (8 Replies)
I noticed in my cron log file for my solaris 8 servers the rc=1. I imagine that is return code and something did not process. Does anyone know what that is, is there fix or the implications of leaving it?
Thank you
> CMD: && /usr/sbin/rtc -c > /dev/null 2>&1
> root 22049 c Fri Dec 19... (1 Reply)
We want to deactivate a VG but failed, because one of the LVs created there is busy. When we are trying to unmount the LV, it is telling "not mounted" and if I execute mount command it will be informing us "already mounted". dmsetup info is indicating "Open Count = 1".
Please help me, how we... (5 Replies)
My volume group of size 200 gb.
out of which only 100 gb is used by 2 logical volumes /dev/vg00/lvol0 and /dev/vg00/lvol0 respectively (both are 50 gb each).
Whenever i use vgreduce command to reduce the size of volume group i get below error.
# vgreduce vg00 -a
Physical volume... (16 Replies)
hi,
I want to create a volume group of 200 GB and then create different file systems on that.
please help me out. Its becomes confusing when the PP calculating PP.
I don't understand this concept. (2 Replies)
Hello.
I am currently on HPUX and migrating to Linux RHEL 6.4
This program on hpux:
/usr/sbin/userdbset
is puzzling me on linux.
Does anyone know the equivilent program forked or used on linux.
This program is mentioned in our user reset script.
here is a strings of the... (2 Replies)
Would some help me on this below
I am trying to extend file system on AIX and however unable to extend the file system.
0516-306 extendvg: Unable to find physical volume 20 in the Device
Configuration Database.
0516-321 extendvg: Physical volume u01-lv is not configured.
0516-792... (15 Replies)
Discussion started by: murali969
15 Replies
LEARN ABOUT HPUX
vxvmboot
vxvmboot(1M)vxvmboot(1M)NAME
vxvmboot - prepare Veritas Volume Manager volume as a root, boot, primary swap or dump volume
SYNOPSIS
/sbin/vxvmboot [-b|-d|-r|-s] [-v] -o offset -l length rawpath
/sbin/vxvmboot -v rawpath
/sbin/vxvmboot -c
DESCRIPTION
The vxvmboot command updates information in the LABEL file for the lif disk specified by the pathname of its character (raw) device node,
rawpath. The volume at the specified offset and length becomes the boot, root, primary swap or dump volume when the system is next booted.
This command is normally invoked by the vxbootsetup utility.
OPTIONS -b Specifies the volume type as a boot volume with name standvol.
-c Is used to update the /stand/rootconf file with the offset and length of the rootvol. The usage is slightly different when the -c
argument is used. The rawpath argument is not used with this invocation. Instead the path of the boot device is extracted from
the /stand/bootconf file. Also, the -o and -l arguments are not used to specify the offset and length. Instead, the offset and
length of the rootvol are obtained from the LIF LABEL file on the boot device.
The -c option would normally be used in the sbin/ioinitrc script to update the /stand/rootconf file, when the boot disk is VxVM
rootable.
-d Specifies the volume type as a dump volume with name dumpvol.
If a dumpvol volume exists on the specified disk, the extent information from this volume is used. If no such volume exists, the
extent information of the swap volume is used instead, and swapvol performs the dual role of swap device and dump device.
-l length Specifies the length of the volume in units of 1024-byte blocks.
-o offset Specifies the start of the volume as the number of 1024-byte blocks from the beginning of the disk.
-r Specifies the volume type as a root volume with name rootvol.
-s Specifies the volume type as a swap volume with name swapvol.
-v When used with one of the options -b, -d, -r or -s, displays the contents of the updated LABEL file. Otherwise, this option may
be used to display the contents of the LABEL file on the specified lif disk.
Note: The -b, -c, -d, -r and -s options are mutually exclusive. If more than one of these options is specified, the vxvmboot com-
mand exits without performing any operation.
ARGUMENTS
rawpath Specifies the pathname of the character (raw) device node for the lif disk.
SEE ALSO lif(4), mkboot(1M), vxbootsetup(1M)VxVM 5.0.31.1 24 Mar 2008 vxvmboot(1M)