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)
:eek:
Hi guys,
I'm pulling my hair out over this one. I am trying to set up a virtual server environment. ( I am using VirtualBox, but I think this is irrelevant to this problem.) I have downloaded a pre-packaged Linux virtual disk, with which I have successfully started a virtual instance of a... (4 Replies)
Hi all,
Fedora 17, 64bit
Ubuntu 12.04 desktop 64bit
HD 160G
I installed Ubuntu 12.04 on the HD first taking up the whole disc. Later I added/installed Fedora 17 selecting the "Shrink" option and save the bootloader on /dev/sda1 to make them dualboot. Installation is successful with... (0 Replies)
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)
Our SAN administrator decided to unpresent then destroy LUN's we were actively using as a volume group (all PV's in said volume group). Now every time I do a pvscan or whatever it complains about I/O errors trying to access those PV's. How do I get it to forget the VG existed completely? vgreduce... (7 Replies)
Good morning,
I'm working in a lab that generates a good amount of data and we've just about filled our 9.1TB RAID.
The system is a Dell PowerEdge 2950 running Scientific Linux 5.4 with a PERC H800 and a Dell PowerVault MD1200. The MD1200 has 12 bays, 6 of which were filled with 2TB drives... (1 Reply)
I am having trouble with LVM and one of my physical volumes.
Using Ubuntu Desktop 14.04
I was trying to set up LVM across two disks (not containing the OS or Home).
First I created the initial Physical Volume, the Volume Group, and the Logical volume, and everything seemed fine. The... (2 Replies)
Hi all,
I added a new disk slice to the current metadb.
Below is what I see
bash-3.2# metadb -i
flags first blk block count
a m p luo 16 8192 /dev/dsk/c0t0d0s7
a p luo 8208 8192 ... (3 Replies)
Discussion started by: javanoob
3 Replies
LEARN ABOUT HPUX
vxvmconvert
vxvmconvert(1M)vxvmconvert(1M)NAME
vxvmconvert - convert LVM volume groups to VxVM disk groups
SYNOPSIS
vxvmconvert
DESCRIPTION
vxvmconvert is a menu-driven program to convert an HP Logical Volume Manger (LVM) configuration to a Veritas Volume Manager configuration.
This man page is a brief overview of vxvmconvert. Refer to the Veritas Volume Manager Migration Guide for a detailed description before
using the conversion procedure.
The vxvmconvert script is interactive and prompts you for responses, supplying defaults where appropriate. There is a Help facility at
every prompt. Enter a question mark (?) at a prompt to display a context-sensitive help message.
With vxvmconvert you can identify LVM volume groups, list disks, analyze volume groups for conversion and complete the conversion of LVM
volume groups to VxVM disk groups.
LVM configurations are converted at the volume group level. All disks used in a volume group are converted together. You cannot use vxvm-
convert to convert unused LVM disks (those not part of an LVM volume group) to VxVM disks. To convert unused LVM disks, use pvremove to
take the disk out of LVM control, then initialize the disk for VxVM use by using vxdiskadm (see pvremove(1M) and vxdiskadm(1M) for more
information).
vxvmconvert changes disks within LVM volume groups to VxVM disks by replacing the areas of the disks used for LVM configuration information
and with the equivalent VxVM volume configuration information. Portions of the disks used for user data, such as file systems and data-
bases, are not affected by the conversion.
The conversion process changes the names by which your system refers to the logical storage, so must be done offline. No applications can
access data in the volume groups undergoing conversion. You must unmount file systems using those volumes and shut down any applications,
such as databases, that might use the volumes directly.
OPERATIONS
Analyze LVM Volume Groups for Conversion
Use this operation to analyze one or more LVM volume groups for conversion to use by VxVM. The analysis checks for problems that
can prevent the conversion from completing successfully. It calculates the space required to add volume group disks to a Volume
Manager disk group. More than one volume group may be entered at the prompt. A grep-like pattern may be used to select multiple
volume groups.
See the ``Limitations in Conversion'' section in the Volume Manager Migration Guide for more information.
Convert LVM Volume Groups to VxVM
Converts one or more LVM volume groups to one or more VxVM disk groups. This adds the disks to a VxVM disk group and replaces
existing LVM volumes with VxVM volumes.
vxvmconvert prompts you to name the VxVM disk group that replaces the LVM volume group being converted. A default is suggested
at the prompt. For example, if you are converting a volume group vg08, vxvmconvert renames it as dg08.
See to the sections ``Dealing with New Logical Volume Names'' and ``Tailoring your VxVM Configuration'' in the Volume Manager
Migration Guide for more information.
Rollback from VxVM to LVM
Rollback reverts VxVM disk groups to LVM volume groups. vxvmconvert provides a limited snapshot capability for the LVM metadata
in a converted volume group. A snapshot is a simple protection method to use during conversion.
Caution! Do not use this operation if the VxVM disk group was modified since the conversion.
See to the section ``Restoring LVM Volume Groups and Disaster Recovery'' in the Volume Manager Migration Guide for more informa-
tion.
List Disk Information
Displays information about the disks on a system. You can obtain detailed information about a disk by entering a specific disk
device address.
List LVM Volume Group Information
Listvg displays a list of LVM volume groups. You can obtain detailed information about an LVM volume group at a specific disk
device address.
SEE ALSO pvremove(1M), vgcfgbackup(1M), vgrestore(1M), vxdisk(1M), vxdiskadd(1M), vxdiskadm(1M), vxintro(1M)
Veritas Volume Manager Migration Guide
VxVM 5.0.31.1 24 Mar 2008 vxvmconvert(1M)