Doh, sorry Matt - you know I didn't even see anything down below where you quoted, my bad. Yeah, I read that you can pvresize (what I'd meant to say), but I was seeing some questionable result via some mail threads. I haven't done it myself to experience success or failure, as I don't typically have contiguous space to reallocate like this. I'm curious the outcome if you want to try, but definitely something to test on a disk, even a thumb drive typically suffices. Adding another partition/pv shouldn't cause any overhead to add the rest of the space to the vg, and that I can quote all day long as successfully done. -mb On Mon, 2009-08-24 at 18:42 -0700, Matt Graham wrote: > From: Michael Butash > >> Or just fdisk the thing, expand the last partition and reboot. No > >> need to make things more complex than necessary. > > That's the thing, I don't think that'll work. > > Which is why I wrote (in the part you failed to quote): > > ------- > Use fdisk to make it larger, reboot, then run pvresize > on the PV, then run lvresize on the LV, then run resize2fs on the > filesystem on the LV. > ------- > > > The PV and subsequent VG and LVM's expect a certain format > > to the blocks of data. Regardless, I think you'll have to prep > > the new, unused space in such a way it's acceptable to LVM > > The man page for pvresize says that's what it does. I don't even > have pvextend on my system here. Did you mean "vgextend"? That's > on a different layer of the LVM system, and is used for the other > (more complicated) approach of making a new PV. > > If you have a spare disk lying around, you can recreate this > approach on that disk and see how it works. A keychain drive > should work fine. > > > I wouldn't be too hasty with toasting my data... > > The OP has a recent backup. Right? > --------------------------------------------------- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss