Sponsored Content
Top Forums UNIX for Advanced & Expert Users Logical Volume Manager question Post 24543 by spawarrior on Sunday 14th of July 2002 02:44:10 PM
Old 07-14-2002
Logical Volume Manager question

After creating a make recover tape on a TAC-4 9000/770, the system lost three of five volume groups from the /etc/lvmtab. What would be the best way to recreate the volume groups in the lvmtab?
 

7 More Discussions You Might Find Interesting

1. AIX

AIX Logical Volume Question

Hi All, There is AIX server which has 2 internal disks running the OS and 8 external disks on a RAID array with RAID 5. My question - is there a way to check which are the logical volumes and file system configured on this RAID array (2 Replies)
Discussion started by: rramanuj
2 Replies

2. AIX

Logical Volume Manager Help

I have a pretty basic question but I am finding my self stumped... I am trying to find the config that shows which logical volume is mapped to which physical volume IE: I know that pdisk15 is mapped to hdisk17 (I only know this as it was told to me though, by IBM) When I run: lslv -p... (5 Replies)
Discussion started by: pheusion
5 Replies

3. UNIX for Advanced & Expert Users

LVM - Extending Logical Volume within Volume Group

Hello, I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB. If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information Regards Himanshu (3 Replies)
Discussion started by: ghimanshu
3 Replies

4. AIX

Basic Filesystem / Physical Volume / Logical Volume Check

Hi! Can anyone help me on how I can do a basic check on the Unix filesystems / physical volumes and logical volumes? What items should I check, like where do I look at in smit? Or are there commands that I should execute? I need to do this as I was informed by IBM that there seems to be... (1 Reply)
Discussion started by: chipahoys
1 Replies

5. Solaris

CLI to get info for Logical Volume manager

What are the comman line instructions need to be used to know if a Logical Volume Manager is installed on solaris Box, What is its name, version, driver version, library version. (1 Reply)
Discussion started by: epriya2003
1 Replies

6. UNIX for Advanced & Expert Users

Veritas Volume Manager question (Disk layout with 4 plexes)

I am trying to build a veritas volume similar to an existing volume on another server. The output on source server is: usbtor12# vxprint -hrtg appdg v anvil_sqlVOL - ENABLED ACTIVE 629145600 SELECT - fsgen pl anvil_sqlVOL-01 anvil_sqlVOL ENABLED ACTIVE 629145600... (3 Replies)
Discussion started by: momin313
3 Replies

7. Red Hat

No space in volume group. How to create a file system using existing logical volume

Hello Guys, I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var. I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies
VGCREATE(8)						      System Manager's Manual						       VGCREATE(8)

NAME
vgcreate - create a volume group SYNOPSIS
vgcreate [-A|--autobackup {y|n}] [-d|--debug] [-h|--help] [-l|--maxlogicalvolumes MaxLogicalVolumes] [-p|--maxphysicalvolumes MaxPhysi- calVolumes] [-s|--physicalextentsize PhysicalExtentSize[kKmMgGtT]] [-v|--verbose] [--version] VolumeGroupName PhysicalVolumePath [Physi- calVolumePath...] DESCRIPTION
vgcreate creates a new volume group called VolumeGroupName using the block special device PhysicalVolumePath previously configured for LVM with pvcreate(8). OPTIONS -A, --autobackup {y|n} Controls automatic backup of VG metadata after the change (see vgcfgbackup(8)). Default is yes. -d, --debug Enables additional debugging output (if compiled with DEBUG). -h, --help Print a usage message on standard output and exit successfully. -l, --maxlogicalvolumes MaxLogicalVolumes Sets the maximum possible logical volume count. More logical volumes can't be created in this volume group. Absolute maximum is 256. -p, --maxphysicalvolumes MaxPhysicalVolumes Sets the maximum possible physical volume count. More physical volumes can't be included in this volume group. Absolute maximum is 256. -s, --physicalextentsize PhysicalExtentSize[kKmMgGtT] Sets the physical extent size on physical volumes of this volume group. A size suffix (k for kilobytes up to t for terabytes) is optional, megabytes is the default if no suffix is present. Values can be from 8 KB to 16 GB in powers of 2. The default of 4 MB causes maximum LV sizes of ~256GB because as many as ~64k extents are supported per LV. In case larger maximum LV sizes are needed (later), you need to set the PE size to a larger value as well. Later changes of the PE size in an existing VG are not supported. -v, --verbose Display verbose runtime information about vgcreate's activities. --version Display tool and IOP version and exit successfully. EXAMPLES
To create a volume group named test_vg using physical volumes /dev/hdk1, /dev/hdl1, and /dev/hdm1 with default physical extent size of 4MB: vgcreate test_vg /dev/sd[k-m]1 NOTE: If you are using devfs it is essential to use the full devfs name of the device rather than the symlinked name in /dev. so: the above could be vgcreate test_vg /dev/scsi/host1/bus0/target[1-3]/lun0/part1 To limit kernel memory usage, there is a limit of 65536 physical extents (PE) per logical volume, so the PE size determines the maximum logical volume size. The default PE size of 4MB limits a single logical volume to 256GB (see the -s option to raise that limit). There is also (as of Linux 2.4) a kernel limitation of 2TB per block device. DIAGNOSTICS
vgcreate returns an exit code of 0 for success and > 0 for error; 1 no volume group and physical volume names on command line 2 no physical volume names on command line 3 invalid volume group name 4 error checking existence of volume group 5 maximum number of volume groups exceeded 6 error reading physical volume(s) 7 invalid physical volume name 8 error getting physical volume size 9 no new physical volume 10 physical volume occurs multiple times on command line 11 memory reallocation error 12 no valid physical volumes on command line 13 some invalid physical volumes on command line 14 physical volume is too small 15 error setting up VGDA 16 error writing VGDA to physical volumes 17 error creating VGDA in kernel 18 error inserting volume group into lvmtab 19 error doing backup of VGDA 20 error writing VGDA to lvmtab 21 volume group directory already exists in /dev 95 driver/module not in kernel 96 invalid I/O protocol version 97 error locking logical volume manager 98 invalid lvmtab (run vgscan(8)) 99 invalid command line ENVIRONMENT VARIABLES
LVM_AUTOBACKUP If this variable is set to "no" then the automatic backup of VG metadata is turned off. LVM_VG_MAX_BACKUPS This variable determines the backup history depth of kept VGDA copy files in /etc/lvmconf. It can be set to a positive number between 0 and 999. The higher this number is, the more changes you can restore using vgcfgrestore(8). SEE ALSO
lvm(8), pvdisplay(8), pvcreate(8), vgdisplay(8), vgextend(8), vgreduce(8), lvcreate(8), lvdisplay(8), lvextend(8), lvreduce(8) AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com> Heinz Mauelshagen LVM TOOLS VGCREATE(8)
All times are GMT -4. The time now is 11:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy