All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Cc: mge@sistina.com
Subject: Re: [linux-lvm] lv_usr not updated after extention
Date: Tue Oct  7 08:50:02 2003	[thread overview]
Message-ID: <20031007153729.B25676@sistina.com> (raw)
In-Reply-To: <OFA250C8DB.F227705D-ONC1256DB4.002ACA22-C1256DB4.002C0295@itet.no>; from Runar.Ingebrigtsen@itet.no on Fri, Oct 03, 2003 at 09:59:35AM +0200

Extending the Logical Volume doesn't automatically extend your filesystem.
Use the filesystem specific resizer, which might require unmounting the filesystem
(e.g. resize2fs for ext2/3 or resize_reiserfs for reiser).

Regards,
Heinz    -- The LVM Guy --

On Fri, Oct 03, 2003 at 09:59:35AM +0200, Runar Ingebrigtsen wrote:
> Hi,
> 
> My system is running with LVM and the VG's vg_system and vg_data.
> 
> Extending any partition in vg_data just works.
> Extending lv_swap in vg_system works.
> But the extended space never shows up in the /usr partition lv_usr! Look 
> yourself:
> 
> #df -h | grep usr
> /dev/vg_system/lv_usr   1.4G  1.3G   82M  95% /usr
> 
> # lvdisplay /dev/vg_system/lv_usr
> --- Logical volume ---
> LV Name         /dev/vg_system/lv_usr
> VG Name         vg_system
> LV Write Access read/write
> LV Status               available
> LV #                    3
> # open                  1
> LV Size                 4.09 GB
> Current LE              131
> Allocated LE            131
> Allocation              next free
> Read ahead sectors      1024
> Block device            58:3
> 
> How come? Is this caused by the /usr partition containing running system 
> files?
> If so, why does the change still not show up after a reboot?
> 
> Now, I would appreciate any help :) Thanks.
> 
> mvh Runar Ingebrigtsen
> 
>       -o)
>       /\\    Message void if penguin violated
>      _\_V    Don't mess with the penguin
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      reply	other threads:[~2003-10-07  8:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07  7:30 [linux-lvm] lv_usr not updated after extention Runar Ingebrigtsen
2003-10-07  8:50 ` Heinz J . Mauelshagen [this message]

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=20031007153729.B25676@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=linux-lvm@sistina.com \
    --cc=mge@sistina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.