Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
roto diskspace 1
- Thread starter TheDash
- Start date
-
1
- #2
hmmm.. I think you are talking about HP-UX.
yes, it does.
Of course:
[tt]vgdisplay -v vg00[/tt]
vg00 is by default the root volume group in hp-ux. You can know what disk drives are in use in a particular volume group with the [tt]vgdisplay[/tt] command.
[tt]vgdisplay -v voulem_group[/tt]
Cheers.
- Thread starter
- #3
Thanks ... vgdisplay -v vg00 gives info about all logical volumes .. vgdisplay -v vg01 shows lvol1 .. Any reason why vg00 shows all ... I just want to make sure that / is 500 mb only and to make it 2gb we have to add more space to it ...
bdf output shows
Filesystem kbytes used avail %used iused ifree %iuse Mounted on
/dev/vg00/lvol3 524288 56851 438239 11% 3552 116856 3% /
bdf output shows
Filesystem kbytes used avail %used iused ifree %iuse Mounted on
/dev/vg00/lvol3 524288 56851 438239 11% 3552 116856 3% /
you get that info with the bdf command!! why are you not sure!?
do you know how the LVM (Logical Volume Manager) works???
A volume group is conformed for 1 or more physical disk drives, so a volume group is virtually only one drive. Inside this volume group you configure "Logical Volumes" (lvols) that are partitions inside the volume group (or virtual disk drive). each partiton has a size and a filesystem in it. The lvol3 for vg00 has a size of 500 MB (see bdfresult!!!).
If you want to know how many space is free in your Volume Group take a look to the [tt]PE size[/tt] (physical extention) and [tt]PE Free[/tt] in the [tt]vgdisplay[/tt] command.
Ok, so after you have this information you can [tt]lvextend[/tt] the lvol and then [tt]extendfs[/tt] (extend filesystem).
the only problem is: you are talking about the roor directory, so you need to boot with a CD or in single user (if I remember).
man vgdisplay
man vgextend
man lvextend
man extendfs
Cheers.
the only problem is: you are talking about the roor directory, so you need to boot with a CD or in single user (if I remember).
man vgdisplay
man vgextend
man lvextend
man extendfs
Cheers.
- Thread starter
- #7
Thanks.
VG Name /dev/vg00
PE Size (Mbytes) 4
Total PE 8680
Alloc PE 6702
Free PE 1978
The max space that /dev/vg00 can get using lvextend is 4GB. so i think after using extendfs, the max space that root (/dev/vg00/lvol3) can get is 4gb. I should actually make it 6 gb. Is it possible? Thanks.
VG Name /dev/vg00
PE Size (Mbytes) 4
Total PE 8680
Alloc PE 6702
Free PE 1978
The max space that /dev/vg00 can get using lvextend is 4GB. so i think after using extendfs, the max space that root (/dev/vg00/lvol3) can get is 4gb. I should actually make it 6 gb. Is it possible? Thanks.
- Thread starter
- #8
Hmm, it is perhaps advisable to consider why root is 6GB.
People have different ways opf doing things, however, I've found (and my company) that / is small, say 300 - 350 MB, why, because everything below that is important /opt, /var, /var/spool and so on are filesystems.
Also, we keep all filesystem in vg00 below 50% at build - this provides room for growth.
Why do we keep root small, well, be making sure everything that is dynamic is not part of the root filesystem ensures that if some area does become full, it isn't root ... as this could possible stop the box running.
I appreciate that this way isn't everyones cup of tea, however, we have a lot of servers >1000 and need to avoid full file systems as much as possible due to the ampount of time we would lose. Also, root disks these days are quite big (typically 73GB) so as we do not put applications on root disks there is plenty of space for generous file system sizes. Pls. see below.
Martin
eg.
/dev/vg00/lvol3 385024 88584 294144 23% /
/dev/vg00/lvol1 298928 59680 209352 22% /stand
/dev/vg00/lvol7 1048576 61739 925726 6% /var
/dev/vg00/lvol12 1048576 17723 966580 2% /var/spool
/dev/vg00/lvol11 1048576 56768 929880 6% /var/opt/perf
/dev/vg00/lvol10 106496 48113 58383 45% /var/opt/metron
/dev/vg00/lvol9 2097152 954687 1071122 47% /var/adm/sw
/dev/vg00/lvol8 8388608 122744 8007564 2% /var/adm/crash
/dev/vg00/lvol6 3145728 1163088 1967192 37% /usr
/dev/vg00/lvol5 1048576 16504 1025456 2% /tmp
/dev/vg00/lvol4 4194304 1796680 2378944 43% /opt
People have different ways opf doing things, however, I've found (and my company) that / is small, say 300 - 350 MB, why, because everything below that is important /opt, /var, /var/spool and so on are filesystems.
Also, we keep all filesystem in vg00 below 50% at build - this provides room for growth.
Why do we keep root small, well, be making sure everything that is dynamic is not part of the root filesystem ensures that if some area does become full, it isn't root ... as this could possible stop the box running.
I appreciate that this way isn't everyones cup of tea, however, we have a lot of servers >1000 and need to avoid full file systems as much as possible due to the ampount of time we would lose. Also, root disks these days are quite big (typically 73GB) so as we do not put applications on root disks there is plenty of space for generous file system sizes. Pls. see below.
Martin
eg.
/dev/vg00/lvol3 385024 88584 294144 23% /
/dev/vg00/lvol1 298928 59680 209352 22% /stand
/dev/vg00/lvol7 1048576 61739 925726 6% /var
/dev/vg00/lvol12 1048576 17723 966580 2% /var/spool
/dev/vg00/lvol11 1048576 56768 929880 6% /var/opt/perf
/dev/vg00/lvol10 106496 48113 58383 45% /var/opt/metron
/dev/vg00/lvol9 2097152 954687 1071122 47% /var/adm/sw
/dev/vg00/lvol8 8388608 122744 8007564 2% /var/adm/crash
/dev/vg00/lvol6 3145728 1163088 1967192 37% /usr
/dev/vg00/lvol5 1048576 16504 1025456 2% /tmp
/dev/vg00/lvol4 4194304 1796680 2378944 43% /opt
- Status