From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j212M9K30526 for ; Mon, 28 Feb 2005 21:22:09 -0500 Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx3.redhat.com (8.12.11/8.12.11) with ESMTP id j212M3a2002234 for ; Mon, 28 Feb 2005 21:22:03 -0500 Received: by wproxy.gmail.com with SMTP id 36so56410wri for ; Mon, 28 Feb 2005 18:21:58 -0800 (PST) Message-ID: <45ae90370502281821514a77c2@mail.gmail.com> Date: Mon, 28 Feb 2005 21:21:58 -0500 From: Jeff Macdonald Subject: Re: [linux-lvm] Adding a disk to a VG gone bad - need help In-Reply-To: Mime-Version: 1.0 Content-Transfer-Encoding: 7bit References: <45ae9037050225202249decf7a@mail.gmail.com> Reply-To: Jeff Macdonald , LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" To: "M. Matt Colgin" Cc: LVM general discussion and development On Mon, 28 Feb 2005 10:19:46 -0800, M. Matt Colgin wrote: > Weird, I'm not totally following how/what happened, but it sounds like > you VG went from 1 PV to 3 (but maybe you started off with two). Yes, I started with 2. > Hopefully you don't have some super important data on it. If you do, > there are some people with more knowledge than me, repost your > question with some more/updated information. > Just all my digial media! :( > Each LVM command will write a "changelog" to the /etc/lvm/archive/* > directory with the state of the VG before/after the command was > issued. The best bet to undo the extend would be to issue a > vgcfgrestore with the file, before your vgextend. Well, with Fedora Core 3, this isn't possible, because that data was stored on a LV. They should make it a symlink to /boot like grub is. This was a disk that was being used as a normal non LVM disk. So it was properly working while copying data from it to a LV. After all the data was transferred, I wanted to add it to the existing VG. See procedures I followed from the previous mail below. As I outlined before, it seems that doing: vgreduce --removemissing VolGroup00 may do the trick, but in test mode I see this troubling line: Removing LV Home from VG Which is definately not what I want. However, perhaps rerunning pvcreate -u with the UUID it claims it doesn't have a device for is a viable alternative? > On Fri, 25 Feb 2005 23:22:59 -0500, Jeff Macdonald > wrote: > > Hi, > > I have one volume group and that is used as such: > > [root@jeff ~]# /usr/sbin/lvscan > > ACTIVE '/dev/VolGroup00/Root' [9.78 GB] inherit > > ACTIVE '/dev/VolGroup00/Home' [231.31 GB] inherit > > ACTIVE '/dev/VolGroup00/Swap' [320.00 MB] inherit > > > > I added a whole disk to VolGroup00 like so: > > [root@jeff ~]# dd if=/dev/zero of=/dev/hde bs=512 count=1 > > 1+0 records in > > 1+0 records out > > > > created the physical volume: > > [root@jeff ~]# /usr/sbin/pvcreate /dev/hde > > > > added it to the volume group: > > [root@jeff ~]# /usr/sbin/vgextend VolGroup00 /dev/hde > > > > added 100G from the 150G drive to Home: > > [root@jeff ~]# /usr/sbin/lvextend -L+100G /dev/VolGroup00/Home > > Extending logical volume Home to 331.31 GB > > Logical volume Home successfully resized > > > > At this point the docs suggest umounting the logical volume in order > > to resize the file system. So I decided I was going to reboot the > > computer and start it into single user mode. When doing that I'm > > greated with: > > > > lvm exited abnormally! > > Couldn't find device with uuid > > Couldn't find all physical volumes for volume group VolGroup00 > > > > So it seems that it can't find the new physical volume that I just > > added. LVM is totally new to me, so any pointers would be great. > > Booting from CD into rescue mode I wasn't unable to get very far. I > > was able to run lvm and pvscan shows this interesting line: > > > > PV /dev/hdf1 VG VolGroup00 lvm2 [ X GB / X GB free] > > PV /dev/hdg2 VG VolGroup00 lvm2 [ Y GB / Y GB free] > > PV unknown device VG VolGroup00 lvm2 [ Z GB / Z GB free] > > Total: 3 [ X GB ] / in use 3 > > > > It seems to be that vgreduce is what I want in order to start over, > > but running this in test mode with -t and --removemissing I see this > > worrying line: > > Removing LV Home from VG > > > > and the line I want > > Removing PV with UUID {correct UUID} > > > > Am I on the right track? > > > > TIA -- Jeff Macdonald Ayer, MA