From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx1.redhat.com (ext-mx01.extmail.prod.ext.phx2.redhat.com [10.5.110.5]) by int-mx08.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id n9LMsQBQ023102 for ; Wed, 21 Oct 2009 18:54:26 -0400 Received: from mail-fx0-f217.google.com (mail-fx0-f217.google.com [209.85.220.217]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n9LMrqnG025838 for ; Wed, 21 Oct 2009 18:54:09 -0400 Received: by mail-fx0-f217.google.com with SMTP id 17so3239977fxm.3 for ; Wed, 21 Oct 2009 15:54:09 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 21 Oct 2009 18:54:08 -0400 Message-ID: <59ac317e0910211554p342c06b2p6d2a17e69fae7364@mail.gmail.com> Subject: Re: [linux-lvm] Total free space using added VGs and LVs From: David Content-Type: multipart/alternative; boundary=001485f6cff84635ec047679db38 Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: To: LVM general discussion and development --001485f6cff84635ec047679db38 Content-Type: text/plain; charset=ISO-8859-1 Is there anyway to recover a lost VolGroup if I have the UUID? thanks, David On Wed, Oct 21, 2009 at 3:03 PM, Lou Arnold wrote: > I read the How-To. It doesn't talk about the specific case or being mounted > at root, so I had to experiment. It is likely that commands were in the > wrong order, but I don't know what the right order is. > > I have attached the terminal session I used. In the end it did not work. > There was still 66 GB free, and when I rebooted, the file system failed. The > superblock was too big. > > I obviously don't understand the difference between pvresize, lvreduce and > vgreduce, and how resize2fs is related to these commands. > > Hope you can help, > Lou. > > > On 10/21/09, Drew wrote: >> >> > The documentation wasn't specific. I believe the intent was simply to >> > migrate the data to another logical volume to temporarily allow the >> source >> > volume to be reduced and/or removed. But let's assume that has happened >> or >> > that doesn't need to happen. So now we need to unmount LogVol00, reduce >> it >> > to its original nunber of extents and then remount it (either before or >> > after remount we remove the physical drive.) I assume you can't try this >> or >> > you'll screw up your computer, but I have a system that I screw up and >> > easily restore from a OS image. So no need to be too cautious. >> >> I've done this on several occasions. >> >> If you want to play with various scenarios in LVM, I'd recommend >> reading the LVM How-To @ http://tldp.org/HOWTO/LVM-HOWTO/ . Sections >> 11 & 13 cover the most common tasks you'll encounter in LVM. Play >> around, don't be afraid to break things, and if you have questions >> feel free to give the list a shout. >> >> >> -- >> Drew >> >> "Nothing in life is to be feared. It is only to be understood." >> --Marie Curie >> > > > _______________________________________________ > linux-lvm mailing list > linux-lvm@redhat.com > https://www.redhat.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ > --001485f6cff84635ec047679db38 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Is there anyway to recover a lost VolGroup if I have the UUID?
=A0

thanks,
David
On Wed, Oct 21, 2009 at 3:03 PM, Lou Arnold <larnolda1@gmail.co= m> wrote:
I read the How-To. It doesn't talk about the specific case or bein= g mounted at root, so I had to experiment. It is likely that=A0commands wer= e=A0in the wrong order, but I don't know what the right order is.
=A0
I have attached the terminal session I used. In the end it did not wor= k. There was still 66 GB free, and when I rebooted, the file system failed.= The superblock was too big.
=A0
I obviously don't understand the difference between pvresize, lvre= duce and vgreduce, and how=A0 resize2fs=A0 is related to these commands.
=A0
Hope you can help,
Lou.

=A0
On 10/21/09, Drew <drew.= kay@gmail.com> wrote:=20
> The documentation wasn'= t specific. I believe the intent was simply to
> migrate the data to = another logical volume to temporarily allow the source
> volume to be reduced and/or removed. But let's assume that has hap= pened or
> that doesn't need to happen. So now we need to unmount= LogVol00, reduce it
> to its original nunber of extents and then rem= ount it (either before or
> after remount we remove the physical drive.) I assume you can't tr= y this or
> you'll screw up your computer, but I have a system th= at I screw up and
> easily restore from a OS image. So no need to be = too cautious.

I've done this on several occasions.

If you want to play wit= h various scenarios in LVM, I'd recommend
reading the LVM How-To @ <= a href=3D"http://tldp.org/HOWTO/LVM-HOWTO/" target=3D"_blank">http://tldp.o= rg/HOWTO/LVM-HOWTO/ . Sections
11 & 13 cover the most common tasks you'll encounter in LVM. Playaround, don't be afraid to break things, and if you have questionsfeel free to give the list a shout.


--
Drew

"Not= hing in life is to be feared. It is only to be understood."
--Marie Curie


_______________________________= ________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/= listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

--001485f6cff84635ec047679db38--