public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Ross Boylan <ross@biostat.ucsf.edu>
To: Freddie Cash <fjwcash@gmail.com>
Cc: ross@biostat.ucsf.edu, kvm@vger.kernel.org
Subject: Re: expanding virtual disk based on lvm
Date: Tue, 28 Aug 2012 14:33:39 -0700	[thread overview]
Message-ID: <1346189619.26275.36.camel@corn.betterworld.us> (raw)
In-Reply-To: <CAOjFWZ46=aCHOj0mP2LoHus_NzFbMpovOkY6Zo-4KkdjA+P8-g@mail.gmail.com>

On Tue, 2012-08-28 at 14:15 -0700, Freddie Cash wrote:
> On Tue, Aug 28, 2012 at 1:26 PM, Ross Boylan <ross@biostat.ucsf.edu> wrote:
> > My vm launches with -hda /dev/turtle/VD0 -hdb /dev/turtle/VD1, where VD0
> > and VD1 are lvm logical volumes.  I used lvextend to expand them, but
> > the VM, started after the expansion, does not seem to see the extra
> > space.
> 
> You've increased the size of the hard drive, but you haven't changed
> the filesystem on top of the hard drive to use that extra space.
> 
> How you do that depends on whether the virtual disks are partitioned
> with filesystems in the partitions; or formatted with a filesystem
> directly.
The virtual disks are partitioned.
> 
> If they are partitioned, then you need to boot off a LiveCD, extend
> the partition, then extend the filesystem in the partition.
So I edit the parition table  directly?  I thought there might be some
meta-information that kvm used to establish the size of the physical
disk.

I'm not sure what the final sector number should be; I could get it
approximately from the size, but I'm not sure my calculation would be
just right.
> 
> If they are formatted directly, then (depending on the filesystem) you
> can grow the filesystem.  Some filesystems can't be extended live, so
> you have to boot to a LiveCD.
> 
> No fancy VM-related tools required.  Just think in terms of real,
> physical hardware, and it all becomes clear.  :)
My real physical disks have never grown spontaneously. :)  I also wasn't
sure how the kernel would react, and so I shut it down during the
growth.

Ross


  reply	other threads:[~2012-08-28 21:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-28 20:26 expanding virtual disk based on lvm Ross Boylan
2012-08-28 21:15 ` Freddie Cash
2012-08-28 21:33   ` Ross Boylan [this message]
2012-08-28 21:33 ` Matthew Patton
2012-08-28 21:40   ` Freddie Cash
2012-09-04 12:53 ` Avi Kivity
2012-09-04 18:58   ` Ross Boylan
2012-09-05  7:25     ` Avi Kivity
2012-09-05  9:15       ` Alexandre DERUMIER

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1346189619.26275.36.camel@corn.betterworld.us \
    --to=ross@biostat.ucsf.edu \
    --cc=fjwcash@gmail.com \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox