public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Gentoo LVM Newbie Question
Date: Thu, 23 Feb 2006 14:41:17 -0600	[thread overview]
Message-ID: <200602231441.17494.bss03@volumehost.com> (raw)
In-Reply-To: <8D0AE50C52974F4AA9971F5C25A0345938A733@murph.madison.local>

On Thursday 23 February 2006 14:22, "CR Little" <crlittle@sourcelink.com> 
wrote about '[gentoo-user] Gentoo LVM Newbie Question':
> I'm having a problem with LVM.
>
> I setup a volume group it had 5.91G in Free PE/Size now states 0/0
> I have a logical volume inside that I tried to extend
> It now states 10.91 GB for LV Size. This lv is mounted to /home when I
> ran lvextend -L+5.91G /dev/vg/home it extended the lv but when you run
> df-h it doesn't show an increased size.
>
> /dev/mapper/vg-home   5.0G  1.6G  3.2G  33% /home
>
> Apparently I missed a step and can't find any information on how to fix
> this. Doesn't it need to know how to format and add the LV extention?

That's an easy one.  But an easy thing to miss, especially if you are new.

df reports the free space on the /filesystem/
lvextend changes the size of the /block device/

Now that your block device is bigger, you need to extend the filesystem to 
use that new space.

What filesystem are you using?

Also, in the future, I believe EVMS can do this all with one command and 
there is a nice ncurses interface.

-- 
Boyd Stephen Smith Jr.
bss03@volumehost.com
ICQ: 514984 YM/AIM: DaTwinkDaddy
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-02-23 20:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23 20:22 [gentoo-user] Gentoo LVM Newbie Question CR Little
2006-02-23 20:41 ` Boyd Stephen Smith Jr. [this message]
2006-02-23 20:59 ` Alexander Skwar
2006-02-23 21:15 ` Qv6
2006-02-23 21:59 ` John Jolet
2006-02-23 22:35   ` Boyd Stephen Smith Jr.
2006-02-24  6:03   ` Alexander Skwar
2006-02-25  3:35     ` Zac Slade
2006-02-25  4:13       ` John Jolet
2006-02-25  4:32         ` Zac Slade
2006-02-25  5:14           ` John Jolet
2006-02-25  6:52             ` Alexander Skwar
2006-02-25  6:44         ` Alexander Skwar
2006-02-25  6:43       ` Alexander Skwar
2006-02-25 11:24         ` Holly Bostick
2006-02-25 12:21           ` Alexander Skwar
2006-02-25  7:55       ` Jarry
2006-02-25 10:26         ` Alexander Skwar
2006-02-25 10:44           ` Jarry
2006-02-25 11:11             ` Alexander Skwar
2006-02-25 15:01             ` [gentoo-user] [OT] " Boyd Stephen Smith Jr.
2006-02-27  6:48             ` [gentoo-user] " Dirk Heinrichs
2006-02-28  5:01               ` Zac Slade
2006-02-28  9:03                 ` Dirk Heinrichs
2006-02-28  9:23                   ` Zac Slade
2006-02-28  9:29                 ` Boyd Stephen Smith Jr.
2006-02-28 13:53                   ` Dirk Heinrichs
  -- strict thread matches above, loose matches on Subject: below --
2006-02-23 20:58 CR Little
2006-02-23 21:36 ` Boyd Stephen Smith Jr.
2006-02-23 21:41 CR Little
2006-02-23 23:29 CR Little
2006-02-23 23:57 ` Boyd Stephen Smith Jr.
2006-02-24 14:40 CR Little

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=200602231441.17494.bss03@volumehost.com \
    --to=bss03@volumehost.com \
    --cc=gentoo-user@lists.gentoo.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