11-05-2010
All of that could be learned by reading the documentation. Default extent size is 4M, it's changeable, although with some caveats, and some distributions use other default values when creating a volume group in the installer.
10 More Discussions You Might Find Interesting
1. HP-UX
hi,
i have a query regarding the size of the LVM header. Since the LVM header of a bootable disk is always 2912KB. The header size of a non bootable disk is not fixed. In Bootable disk after the LVM header (2912 KB=5824 sectors)the user data starts or we can say LV extents starts.
If i extend any... (0 Replies)
Discussion started by: gorayen
0 Replies
2. Solaris
hi all,
in my server there are some specific application files which are spread through out the server... these are spread in folders..sub-folders..chid folders...
please help me, how can i find the total size of these specific files in the server... (3 Replies)
Discussion started by: abhinov
3 Replies
3. HP-UX
When i run dmesg, I get the following message which clearly indicates that the file system is full. Please let me know what does (1 block extent) means in the following error message?
msgcnt 1 vxfs : mesg 001: vx_nospace - /dev/vg00/lvol4 file system full (1 block extent)
Thanks (6 Replies)
Discussion started by: Adams Nave
6 Replies
4. HP-UX
Hi,
I'm new to HP-UX.
I have LVM on /var with 92Gig. I would like to reduce it to create another LVM for Oracle client with 800 meg or so. How to do it. I'm running 11.iv3
Thanks (4 Replies)
Discussion started by: lamoul
4 Replies
5. Shell Programming and Scripting
#!/bin/sh
##########################################################################################################
#This script is being used for AOK application for cleaning up the .out files and zip it under logs directory.
# IBM
# Created
#For pdocap201/pdoca202 .out files for AOK
#1.... (0 Replies)
Discussion started by: mridul10_crj
0 Replies
6. Shell Programming and Scripting
Hi Experts,
I have a script like
$ORACLE_HOME/bin/sqlplus username/password # << ENDSQL
set pagesize 0 trim on feedback off verify off echo off newp none timing off
set serveroutput on
set heading off
spool Schemaerrtmp.txt
select ' TIMESTAMP COMPUTER NAME ... (5 Replies)
Discussion started by: welldone
5 Replies
7. Solaris
Hi guys!
Could you tell me what's this figure about? (See the attached figure below.)
This is a representation of block allocation filesystem and extent allocation filesystem in Solaris.
Does this mean that in a block-based allocation, data are placed in individual blocks while in... (0 Replies)
Discussion started by: arah
0 Replies
8. UNIX for Dummies Questions & Answers
Hi Guys,
I m using redhat 6, I have installed root partition as non-LVM .
Is there any way i can convert it to LVM? (1 Reply)
Discussion started by: pinga123
1 Replies
9. UNIX for Advanced & Expert Users
Hello,
in one default UFS filesystem we have 8K block size (bsize) and 1K fragmentsize (fsize). At this scenary I thought all "FileSytem IO" will be 8K (or greater) but never smaller than the fragment size (1K). If a UFS fragment/blocksize is allwasy several ADJACENTS sectors on disk (in a ... (4 Replies)
Discussion started by: rarino2
4 Replies
10. Red Hat
Hi All,
I have one logical volume with size as 900G and it is mounted as xfs file system.
Now I want to reduce this partition to 500G.
So I followed the below steps.
unmount the mount point /home
Reduced the volume using the command
Now I remounted the partition.
But the problem... (3 Replies)
Discussion started by: kalpeer
3 Replies
lvmpvg(4) Kernel Interfaces Manual lvmpvg(4)
NAME
lvmpvg - LVM physical volume group information file
SYNOPSIS
DESCRIPTION
is an ASCII file that stores the volume-group information for all of the physical volume groups in the system. The information is stored
in a hierarchical format.
First, it starts with a volume group under which multiple physical volume groups can exist. Under each physical volume group, a list of
physical volumes can be specified. There must be at least one physical volume group in each volume group that appears in this file. The
physical-volume-group name must be unique within the corresponding volume group, although it is permissible to use a common physical volume
group name across different volume groups. There can be as many volume groups in this file as there are in the system.
Instead of using the and commands, the administrator can edit this file to create and extend physical volume groups. However, care must be
taken to ensure that all physical volumes to be included in the file have already been defined in their respective volume groups by previ-
ous use of or
The file format has the following structure. and are keywords that introduce the names of the volume group and physical volume group,
respectively.
pv_path
...
pv_path
...
pv_path
...
The variables are defined as follows:
pv_path The block device path name of a physical volume within the volume group.
pvg_name The name of the physical volume group. It must be unique within the volume group.
vg_name The path name of the volume group.
EXAMPLES
The following example shows an file containing two volume groups: the first containing two physical volume groups, each with two physical
volumes defined in it; the second containing three physical volume groups, each with one physical volume defined in it.
SEE ALSO
vgcreate(1M), vgextend(1M), vgreduce(1M), vgremove(1M), intro(7), lvm(7).
lvmpvg(4)