Expanding a volume group with system-config-lvm Post: 302767099

Sponsored Content

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

02-06-2013

Registered User

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

mmulqu

View Public Profile for mmulqu

Find all posts by mmulqu

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

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?

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 ?)

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

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

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

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.

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

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

LEARN ABOUT CENTOS

vgrename

VGRENAME(8)						      System Manager's Manual						       VGRENAME(8)

NAME

       vgrename - rename a volume group

SYNOPSIS

       vgrename   [-A|--autobackup   {y|n}]   [-d|--debug]   [-h|-?|--help]   [-t|--test]  [-v|--verbose]  OldVolumeGroup{Path|Name|UUID}  NewVol-
       umeGroup{Path|Name}

DESCRIPTION

       vgrename renames an existing (see vgcreate(8)) volume group from OldVolumeGroup{Name|Path|UUID} to NewVolumeGroup{Name|Path}.

       All the Volume Groups visible to a system need to have different names.	Otherwise many LVM2 commands will refuse to run  or  give  warning
       messages.

       This situation could arise when disks are moved between machines.  If a disk is connected and it contains a Volume Group with the same name
       as the Volume Group containing your root filesystem the machine might not even boot correctly.  However, the two Volume Groups should  have
       different UUIDs (unless the disk was cloned) so you can rename one of the conflicting Volume Groups with vgrename.

OPTIONS

       See lvm(8) for common options.

Examples
       Renames existing volume group vg02 to my_volume_group:

       vgrename /dev/vg02 /dev/my_volume_group

       or

       vgrename vg02 my_volume_group

       Changes the name of the Volume Group with UUID
       Zvlifi-Ep3t-e0Ng-U42h-o0ye-KHu1-nl7Ns4 to VolGroup00_tmp:

       vgrename Zvlifi-Ep3t-e0Ng-U42h-o0ye-KHu1-nl7Ns4 VolGroup00_tmp

SEE ALSO

       lvm(8), vgchange(8), vgcreate(8), lvrename(8)

Sistina Software UK				     LVM TOOLS 2.02.105(2)-RHEL7 (2014-03-26)					       VGRENAME(8)

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

LVM - Extending Logical Volume within Volume Group

Discussion started by: ghimanshu

2. AIX

Moving a Logical Volume from one Volume Group to Another

Discussion started by: krisw

3. AIX

activating volume group on system after higher level aix installation

Discussion started by: astjen

4. AIX

Logical volume name conflict in two volume group

Discussion started by: dantares