linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Sean Boyd <sboyd@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvextend
Date: Thu, 23 Jun 2005 11:08:21 +1000	[thread overview]
Message-ID: <1119488901.4305.27.camel@sboyd.brisbane.redhat.com> (raw)
In-Reply-To: <200506221716.00221.t-rigby@shaw.ca>

On Wed, 2005-06-22 at 17:16 -0700, Terry Rigby wrote:
> I am trying to add a full hard drive to my LV by following the directions at 
> TLDP.org.  It says there to use lvextend -L +XXG where XX is the size in GB 
> you want to add to the LV.  Is there a more simple way to just add a whole 
> hard drive ie: /dev/hde
> 
> It seems like a pain to have to manually figure out the size of the hard drive 
> then add it using lvextend -L +200GB for a 200GB hard drive especially since 
> we all know its not actually 200GB.

You could increase the LV by using the remaining free physical extents
(PE).

To check how many PE's are available after extending the VG run
vgdisplay and check "Free  PE / Size". The first value will give you the
total number of PE's available.

Then extend your LV using the -l switch to specify PE's rather than
having to determine a size using the -L switch.

For example "lvextend -l +25 /dev/volGroup00/myLVM" will extend myLVM by
25 PE's.

Of course you then need to extend to file system to be able to use this
extra space :)

--Sean

  parent reply	other threads:[~2005-06-23  1:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23  0:16 [linux-lvm] lvextend Terry Rigby
2005-06-23  0:30 ` dean gaudet
2005-06-23  1:08 ` Sean Boyd [this message]
2005-06-23  1:13   ` Terry Rigby
  -- strict thread matches above, loose matches on Subject: below --
2004-10-14  6:56 Bengt Heijnesson
2003-05-10  8:38 Joerg.Redlich
1999-12-31 19:46 Heinz Mauelshagen
1999-12-28 19:09 Adam Crews
1999-12-29 10:06 ` Fabian Herschel
1999-12-29 20:50   ` Adam Crews
1999-12-30 21:13     ` Torsten Neumann

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=1119488901.4305.27.camel@sboyd.brisbane.redhat.com \
    --to=sboyd@redhat.com \
    --cc=linux-lvm@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).