Sponsored Content
Operating Systems Linux LVM (volume manager) and virtual disks Post 302317148 by otheus on Monday 18th of May 2009 07:23:08 AM
Old 05-18-2009
Thanks, mark54g. I read up on vgimport, and this didn't seem to be what I needed. Anyway, I decided to approach my problem differently: by using a Linux-recovery-DVD/ISO from which to boot the VM. This works and didn't cause configuration headaches.
 

9 More Discussions You Might Find Interesting

1. Linux

Problem for restoring lvm on different disks

Hi all, I have a server running in RH ES4, the SCSI HD are running in RAID 1. I backup the LVM config by using 'vgcfgbackup' and then remove all the HD. I insert another HD (same size & branch but different model) into the machine and run linux rescue to recreate the... (0 Replies)
Discussion started by: donaldfung
0 Replies

2. 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

3. Solaris

How to resize mirror volume in veritas volume manager 3.5 on Solaris 9 OE

Hi all, I have a problem with vxvm volume which is mirror with two disks. when i am try to increase file system, it is throwing an ERROR: can not allocate 5083938 blocks, ERROR: can not able to run vxassist on this volume. Please find a sutable solutions. Thanks and Regards B. Nageswar... (0 Replies)
Discussion started by: nageswarb
0 Replies

4. SuSE

Remove disks from VGs in LVM

Hi, I have following set up on Open suse 11 vgdisplay pvdisplay lvdisplay I would like to remove these disks /dev/sdb and /dev/sdc from LVM and do not use them for anything.. Can anyone please help me with this ? (1 Reply)
Discussion started by: upengan78
1 Replies

5. Solaris

RAID manager or veritas volume manager

Can somebody kindly help me to determine which one i should choose to better manipulate OS volume. RAID manager or veritas volume manager? Any critical differences between those two? Thanks in advance. (5 Replies)
Discussion started by: beginningDBA
5 Replies

6. UNIX for Dummies Questions & Answers

VERITAS Volume Manager - mirror a disk/volume

I have a machine (5.10 Generic_142900-03 sun4u sparc SUNW,Sun-Fire-V210) that we are upgrading the storage and my task is to mirror what is already on the machine to the new disk. I have the disk, it is labeled and ready but I am not sure of the next steps to mirror the existing diskgroup and... (1 Reply)
Discussion started by: rookieuxixsa
1 Replies

7. Red Hat

Create volume using LVM over 2 physical disks

I wanted to know how we can combine volumes over 2 physical drives. # fdisk -l Disk /dev/sda: 42.9 GB, 42949672960 bytes 255 heads, 63 sectors/track, 5221 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 ... (16 Replies)
Discussion started by: ikn3
16 Replies

8. Red Hat

Configure LVM to gain access to the data on disks

Hello friends, We had to upgrade RHEL 4.x to 5.7 so we took complete backup. Since DIRECT UPGRADE not possible, we rebuilt 5.7 from scratch. We had lvm configuration on DATA disks in previous OS and now we need to configure such that we should be able to have same old LVM configuration (like... (1 Reply)
Discussion started by: prvnrk
1 Replies

9. Solaris

Disks are not visible in Veritas Volume manager

Hi I have created a new setup for VCS for doing some testing on virtual box. After creating 3 Solaris 10 machine (147148-26) with VCS. Here I have used one machine as ISCSI Storage. VCS Version is bash-3.2# /opt/VRTS/bin/haclus -value EngineVersion 6.0.10.0 bash-3.2# bash-3.2# pkginfo... (4 Replies)
Discussion started by: hb00
4 Replies
vgimport(1M)															      vgimport(1M)

NAME
vgimport - import an LVM volume group onto the system SYNOPSIS
mapfile] vg_name pv_path ... mapfile] infile] vg_name mapfile vg_name DESCRIPTION
The command adds the specified volume group to the system. The physical volumes, specified as pv_path ..., are scanned to obtain the vol- ume group information and logical volume information. This command works much like A user may explicitly create the vg_name directory and the file before importing the volume group. If absent, the command will automatically create the directory and the file, assigning the minor number as explained in the command man page (see vgcreate(1M)). The vg_name is added to the or file, and the associated logical volume device files are added to the system. assumes that the volume group information has already been created on the physical volumes. This command is useful in conjunction with the command (see vgexport(1M)), to move volume groups from one system to other systems within a high availability cluster. creates logical volume device files under the vg_name directory using the naming convention given in mapfile or using the default naming convention used by the command (see lvcreate(1M)). The command reconstructs the newly imported volume group entry in the or file. The order of the disks belonging to the newly imported vol- ume group could be different than it was before. When a bootable volume group is imported (volume groups version 1.0 only), the boot information present in the boot disks might be incor- rect due to the change in the order of disks in the file. This is because the boot information on the boot disks assumes a certain order of disks in and requires a resynchronization of this information after the first activation of a newly imported bootable volume group. To resynchronize the information on the boot disk after the first activation of a newly imported bootable volume group, run the command in recovery mode option). does not activate the imported volume group due to the many possible options at volume group activation time. To activate the volume group once it has been successfully imported, use the command (see vgchange(1M)). Options and Arguments recognizes the following options and arguments: pv_path The block device path names of a physical volume. This argument is not used with the and related options. vg_name The path name of the volume group. Specify the name of the file from which logical volume names and numbers are to be read. This option is optional when used as in the first com- mand line format of the If this option is not specified, logical volume names are created using the default naming convention where is the decimal representation of logical volume minor number. When used with the option, the volume group specified in the mapfile can be shared among the exporting system and the importing systems. Configure the volume group by populating persistent device special files in the or file, corresponding to the volume group, vg_name. (See intro(7) for information about device special files.) This option can only be used with option. If is invoked without a option, legacy device special files will be used to populate the or file. This option may become obsolete in future releases. Scan option. Scan each of the disks connected to the system and update the or file with the physical volumes that have matching volume group information, as found in the mapfile. This option should always be used in conjunction with the option. The specified mapfile is the file gener- ated by running the command, also with and options. Preview the actions to be taken but do not update the or file or add the logical volume device files. This option is best used in conjunction with the option. Print verbose messages including names of the logical volumes. Import the set of pv_paths held in the infile into the volume group. This option is used as an alternative to specifying the pv_paths on the command line. Each pv_path must appear on a new line in the infile. This option may not be used together with the option. WARNINGS
The option may become obsolete in future releases. No more than eight paths to any physical volume will be added to the or file. All other paths wll be omitted. The following warnings apply to the option, when importing disks with alternate paths: The command does not preserve the path ordering, when a volume group is exported and then imported. This may cause the primary and alter- nate paths to be different on an importing system, from that of an exported system. Also, additional alternate paths that were not config- ured on the exported system may get discovered and configured on the importing system. If the original primary path of a disk gets configured as an alternate path after the volume group is imported, the order can easily be reverted by using to remove the primary path and then reconfiguring the same path again as an alternate, using If additional alternate paths were added to the newly imported volume group, use to reduce any alternate paths that were added but not required. EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified or is null, it defaults to "C" (see lang(5)). If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)). EXAMPLES
Import the volume group that is located on physical disks and Activate the volume group following a successful import: Import the volume group using the mapfile, was previously specified by the command on another system. The volume group, is specified in and will be used by the importing system only: Import the volume group using the mapfile, was previously specified by the command on another system. The volume group, is specified in and will be shared among the exporting system, this system, and other systems importing the volume group as shared: Import the volume group using the infile, was previously specified by the command on another system, and it assumes that pv_paths in the are identical on both systems. SEE ALSO
vgexport(1M), vgscan(1M), intro(7), lvm(7). vgimport(1M)
All times are GMT -4. The time now is 10:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy