If the physical volume is still used you will have to migrate the data to another physical volume using pvmove. (But I have nothing to move and no pladce to move anything to.)
Then use 'vgreduce' to remove the physical volume:
# vgreduce my_volume_group /dev/hda1
-- Result: The message says that the PV is busy.
No where does it say how to make it not busy.
I tried "13.5. Removing an Old Disk" but that tries to move physical extents. But again, I have nothing to move, and no place to move anything.
And..the examples show how to remove a disk when the LV is not mounted at root.
So now I have to figure out what to do to make the logical volume not busy and yet still let the computer operate. That last trial wasn't successful, and I really don't know where to start.
I'm new to this list and have not posted here before, so I am not sure
if this is the advice you'd eventually get, but it seems like you should
focus on the basics. You will need to understand the individual
components before a the more task-oriented parts of a how-to will be of
use. Following a step-by-step guide will get you a result, but if you
don't understand the steps the result probably won't be of any use to you.
The how-to has a good breakdown of the anatomy of LVM; that might be the
best place to start, focusing on the differences between Physical
Volumes, Volume Groups, Logical Volumes and where in that arrangement a
filesystem is placed.
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,
> On 10/21/09, *Drew* <drew kay gmail com <mailto:drew kay gmail com>> 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.
> "Nothing in life is to be feared. It is only to be understood."
> --Marie Curie
> linux-lvm mailing list
> linux-lvm redhat com
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
linux-lvm mailing list
linux-lvm redhat com
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/