Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Expanding a volume group with system-config-lvm
Special Forums Hardware Filesystems, Disks and Memory Expanding a volume group with system-config-lvm Post 302767099 by mmulqu on Wednesday 6th of February 2013 07:49:31 AM
Old 02-06-2013
Expanding a volume group with system-config-lvm
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 that made up the original 9.1TB RAID5.

Recently, I purchased 6 new 2TB disks and added them to the 6 empty bays in the MD1200. Then, using Dell OpenManage, I reconfigured the virtual disk, adding the 6 new disks and converting to RAID6. That process took about two weeks and I ended up with about a 18.2TB virtual disk.

Now, the problem I'm having is expanding the volume group, which is still 9.1TB. I'm using the system-config-lvm package. The physical partition with all of my data is /dev/sdb1 and the volume group is called vg-home.

When I select 'vg-home Physical view' it shows me the volume group and a button below it that says 'Extend Volume Group'. I click on that button and a new window (title 'Extend Volume Group') pops up. In this window, one of my choices is /dev/sdb 9312.50GB Uninitialized Disk Entity. The only other choices are my non-LVM /boot and / partitions, /dev/sda1 and /dev/sda3. My understanding is that the uninitialized disk entity on /dev/sdb is all of the newly added, non-LVM disk space.

However, once I click OK, I get a warning that states "All data on disk entity /dev/sdb will be lost! Are you certain that you wish to initialize it?". Unfortunately, I don't have a test system so I want to be absolutely sure I'm doing this correctly. Is this uninitialized disk entity the new space? Does the warning mean that I'll lose the data on the LVM partition /dev/sdb1 as well or is it just saying that, if there is any data in the uninitialized space, it will be erased?

Thank you,
Matt
 

10 More Discussions You Might Find Interesting

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

2. AIX

Moving a Logical Volume from one Volume Group to Another

Does anyone have any simple methods for moving a current logical volume from one volume group to another? I do not wish to move the data from one physical volume to another. Basically, I want to "relink" the logical volume to exist in a different volume group. Any ideas? (2 Replies)
Discussion started by: krisw
2 Replies

3. AIX

activating volume group on system after higher level aix installation

Hi, if I do install aix 5.3 on the rootvg of an aix 4.3.3 system (having rootvg and data1vg), is it possible to varyonvg the data1vg after the installation ? (any caution ?) (1 Reply)
Discussion started by: astjen
1 Replies

4. AIX

Logical volume name conflict in two volume group

Hello, I am a french computer technician, and i speak English just a little. On Aix 5.3, I encounter a name conflict logical volume on two volume group. The first volume lvnode01 is OK in rootvg and mounted. It is also consistent in the ODM root # lsvg -l rootvg |grep lvnode01 ... (10 Replies)
Discussion started by: dantares
10 Replies

5. AIX

Adding a Volume Group to an HACMP Resource Group?

Hi, I have a 2 node Cluster. Which is working in active/passive mode (i.e Node#1 is running and when it goes down the Node#2 takes over) Now there's this requirement that we need a mount point say /test that should be available in active node #1 and when node #1 goes down and node#2 takes... (6 Replies)
Discussion started by: aixromeo
6 Replies

6. UNIX for Dummies Questions & Answers

Confusion Regarding Physical Volume,Volume Group,Logical Volume,Physical partition

Hi, I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies 1)Physical Volume 2)Volume Group 3)Logical Volume 4)Physical Partition Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies

7. Red Hat

Removing LVM Volume Group that doesn't exist anymore

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)
Discussion started by: thmnetwork
7 Replies

8. UNIX for Dummies Questions & Answers

How to create a volume group, logical volume group and file system?

hi, I want to create a volume group of 200 GB and then create different file systems on that. please help me out. Its becomes confusing when the PP calculating PP. I don't understand this concept. (2 Replies)
Discussion started by: kamaldev
2 Replies

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

10. UNIX for Advanced & Expert Users

[REDHAT7] Adding LVM volume

Dear community, is it possible to add more volumes to actual LVM disk? I have the following: # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 120G 0 disk ├─sda1 8:1 0 500M 0 part /boot └─sda2 ... (0 Replies)
Discussion started by: Lord Spectre
0 Replies

LEARN ABOUT HPUX

vxdestroy_lvmroot

vxdestroy_lvmroot(1M)													     vxdestroy_lvmroot(1M)

NAME

       vxdestroy_lvmroot - remove LVM root disk and associated LVM volume group

SYNOPSIS

       vxdestroy_lvmroot [-v] [-b] lvm_root_disk

DESCRIPTION

       The  vxdestroy_lvmroot  command	tears  down  and removes the LVM volume group associated with the specified physical disk. This is done by
       removing the volumes in the volume group and then removing the volume group.

OPTIONS

       -b	 Invokes the setboot command to change the primary boot disk to the VxVM root disk from which the system was booted (if  the  pri-
		 mary  boot  disk is not already set to this disk).  The alternate boot device remains unchanged.  If the -v option is also speci-
		 fied, the settings of the primary and alternate boot devices are displayed.

       -v	 Outputs verbose messages including a timestamp that indicates major operations being performed.

ARGUMENTS

       lvm_root_disk
	    Specifies the device name of the LVM root disk that is to be destroyed, along with its entire volume group.

EXAMPLES

       This example shows the vxdestroy_lvmroot command invoked in its simpliest form:

       /etc/vx/bin/vxdestroy_lvmroot c5t1d0

       # /etc/vx/bin/vxdestroy_lvmroot -v -b c3t0d0
       Are you sure about destroying c3t0d0 (imported on VG /dev/vg02) ? YES
       vxdestroy_lvmroot 06:02: Tearing down /dev/vg02 on device c3t0d0
       vxdestroy_lvmroot 06:02:
	 Unmounting and removing any volumes associated with /dev/vg02
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol1
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol2
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol3
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol4
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol5
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol6
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol7
       vxdestroy_lvmroot 06:02: removing logical volume /dev/vg02/lvol8
       vxdestroy_lvmroot 06:02: Removing Volume Group /dev/vg02
       vxdestroy_lvmroot 06:02: Removing device files in /dev/vg02
       vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c3t0d0
       vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c1t1d3
       vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c1t1d4
       vxdestroy_lvmroot 06:02: Removing LVM Physical Volume c1t1d5
       vxdestroy_lvmroot 06:03: Current setboot values:
       vxdestroy_lvmroot 06:03: Primary:       0/0/6/0/0.0.0
       vxdestroy_lvmroot 06:03: Alternate:     0/0/1/0/0.1.0
       vxdestroy_lvmroot 06:03:
	 Making disk c0t1d0 (0/0/1/0/0.1.0) the primary boot disk
       vxdestroy_lvmroot 06:03:
	 Removal of device c3t0d0, volume group /dev/vg02 was successful

SEE ALSO

       cpio(1), dd(1), fsck(1M), setboot(1M) vxbootsetup(1M) vxcp_lvmroot(1M) vxres_lvmroot(1M)

VxVM 5.0.31.1							    24 Mar 2008 					     vxdestroy_lvmroot(1M)
All times are GMT -4. The time now is 09:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy