<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.24.5">
</HEAD>
<BODY>
Hmm. Yes, what I was doing was reducing the size of /home and /u so that they were in total smaller than the new 1TB disk I bought. <BR>
<BR>
And the LVM GUI interface tells you it has to umount them, and when you ok that, of course it can't unmount them. <BR>
<BR>
So, adding doesn't take a rescue boot. Only problem is I've already stuffed the chassis full, so I'm not likely to be adding drives. I guess I could replace the 1TB drive with a 2TB drive once they get to be $9 each next year. <BR>
<BR>
On Tue, 2012-03-20 at 11:50 -0400, Robert wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
>Now, I've already messed with logging in as root, unmounting /home
>and /u, and resizing both.
>
>However, I had to unmount them in order for the native LVM to be willing
>to do that. which makes perfect sense.
I haven't found that to be the case. I regularly resize /, /home, /usr, etc on
my machines, with no problem. This is for ext* filesystems, I don't know if
other filesystems have more restrictions. It goes something like this:
# lvextend -L +4g /dev/vg/root
# resize2fs /dev/vg/root
It's a little more complicated for shrinking, and I think that you do need a
rescue disk to shrink anything you can't unmount, like /.
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>