linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Tom Dawes-Gamble <tmdg@uksr.hp.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lv extend
Date: Mon, 05 Feb 2001 12:11:45 GMT	[thread overview]
Message-ID: <200102051211.MAA02014@hpwine73.uksr.hp.com> (raw)
In-Reply-To: <3A7E9408.58179E5@qis-systemhaus.de>; from "Dirk Heinrichs" at Feb 5, 101 11:52 am

Hi,

	This seems a Frequent problem we get it on HP-UX LVM too.
People do an lvextend and then wonder why the filesystem has not grown
to fill the lvol.

	Perhaps a message like.

[root@ocalhost /root]# lvextend -l 256 /dev/vg01/lvol2
lvextend -- extending logical volume "/dev/vg01/lvol2" to 1 GB
lvextend -- doing automatic backup of volume group "vg01"
lvextend -- logical volume "/dev/vg01/lvol2" successfully extended

Note:  You need to run a resize utility such as ext2resize before
	the space is available in the file system.

[root@localhost /root]#

Or lvextend could check the mount table and offer to run ext2resize
for you.  If that seems like a neat idea I would be willing to write
the code.

Regards,
Tom.

> 
> James wrote:
> > 
> > Hello
> > 
> > Is it normal after growing an LV not to see the change with df -h ? But it
> > can be seen with vgdisplay -v ?
> Did you also resize the filesystem? df shows filesystem sizes. If so,
> maybe a remount of the filesystem could help.
> 
> Bye...
> 
> 	Dirk
> -- 
> Dirk Heinrichs		| Tel:	+49 (0)241 413 260
> QIS Systemhaus GmbH	| Fax:	+49 (0)241 413 2640
> J�licher Str. 338b	| Mail:	heinrichs@qis-systemhaus.de
> D-52070 Aachen		| Web:	http://www.qis-systemhaus.de
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> 


--
 int/* PROCEDURE DIVISION.*>*/b,g,l,n='/'/'/'<<2;extern void printf();int main
 (int d,char**z){char*o,*c="%.9s%.7s%.7s\n";l=*(c+d+d)-*(c+d);g=*c-d-l;b=l+n++;
   o="  DISPLAY'tmdg@uksr'    '.hp.com' *>"+g++;printf(c,o-b++,o+l,o);l=~++n;
   o="  DISPLAY'http://www.itrc.hp.com/' *>"+g++;printf(c,o-b++,o+l,o);exit();}

  reply	other threads:[~2001-02-05 12:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-05 11:16 [linux-lvm] lv extend James
2001-02-05 11:52 ` Dirk Heinrichs
2001-02-05 12:11   ` Tom Dawes-Gamble [this message]
2001-02-05 12:24     ` James
2001-02-05 18:01       ` Tom Dawes-Gamble
2001-02-05 12:13   ` James
  -- strict thread matches above, loose matches on Subject: below --
2001-02-05 12:37 S. Michael Denton
2001-02-05 12:43 ` James
2001-02-05 12:45 S. Michael Denton
2001-02-05 12:58 ` James
2001-02-05 13:01   ` Jos Visser
2001-02-05 14:10     ` James
2001-02-05 14:16       ` Jos Visser
2001-02-05 14:57         ` James
2001-02-05 22:38     ` Andreas Dilger
2001-02-05 19:34   ` dmeyer
2001-02-05 14:55     ` Richard Smith
2001-02-05 21:37       ` dmeyer
2001-02-05 17:28         ` Richard Smith
2001-02-05 21:17     ` Erik Bågfors
2001-02-05 12:59 ` Patrick Caulfield

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=200102051211.MAA02014@hpwine73.uksr.hp.com \
    --to=tmdg@uksr.hp.com \
    --cc=linux-lvm@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 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).