[linux-lvm] lv extend

[linux-lvm] lv extend

[James]

Hello

Is it normal after growing an LV not to see the change with df -h ? But it
can be seen with vgdisplay -v ?

james@munster:~$ df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/hda1             4.6G  1.5G  2.9G  33% /
/dev/lvdev/home       984M  322M  613M  35% /home
/dev/lvdev/var        984M   91M  843M  10% /var
/dev/lvdev/usr        984M  485M  450M  52% /usr


I added half a gig to /usr ??

--- Logical volume ---
LV Name                /dev/lvdev/usr
VG Name                lvdev
LV Write Access        read/write
LV Status              available
LV #                   2
# open                 1
LV Size                1.46 GB
Current LE             375
Allocated LE           375
Allocation             next free
Read ahead sectors     120
Block device           58:1

Thanks

Re: [linux-lvm] lv extend

[Dirk Heinrichs]

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

Re: [linux-lvm] lv extend

[Tom Dawes-Gamble]

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();}

Re: [linux-lvm] lv extend

[James]

> > 
> > 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.

All I did was lvextend -L+500 /dev/lvdev/usr I have just realised from the
DOC (it isn't clear that I have to do the ex2resize stuff.) It says if I
want to do it manually to use ex2resize, is thare another way?


 
> 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
> 

Re: [linux-lvm] lv extend

[James]

That would be great :-)

On Mon, 5 Feb 2001, Tom Dawes-Gamble wrote:

> 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();}
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> 

RE: [linux-lvm] lv extend

[S. Michael Denton]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Speaking as one with extensive experience with LVM on nearly every
major unix vendor, it is not a -problem- but more of a lack of
knowledge on the user/administrator's part.  As I recall, the
documentation clearly notes that a filesystem that resides on an lv
must be extended after extending the lv else the OS will not address
the newly-allocated space.  IMHO it would be a -very- bad idea to
automatically run ext2resize as not everyone uses ext2 on lvm and I
think repeated offers to ask if you want to resize this ext2
filesystem (that perhaps isn't even a filesystem at all) would get
terribly annoying and NT-ish.  Also there's the issue with
reduction... if you reduce an lv, LVM (linux LVM is not different
than the other major unixes either) assumes that you have already
reduced any filesystems, tablespaces, etc that might be using that
space before you do the reduction.  Automatic reduction of a
filesystem can be extraordinarily dangerous.

Perhaps as a compromise it could be a configuration flag in some lvm
config file as to whether or not to automatically/offer to/never
resize filesystems after extension/reduction.

Just a thought...

On Monday, 05 February 2001 07:25, James [SMTP:james@fr.clara.net]
wrote:
> 
> That would be great :-)
> 
> On Mon, 5 Feb 2001, Tom Dawes-Gamble wrote:
> 
> > 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();}
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm


Scott Denton
smdenton@bellsouth.net
EFnet Handle: SteelWyng
ICQ UIN: 24149258
AIM Screen Name: SteelWyng

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBOn6ehnC+DNfF0nVpEQJHSACcCDGbtHNQW+j+4uNASe7YvM4aUUgAnjtb
XiRAAN7W/5HQFuSbly6U3EK5
=FTvP
-----END PGP SIGNATURE-----

RE: [linux-lvm] lv extend

[James]

Yes, I do have to agree. By reading the Doc I did quickly realize my
error. The idea of printing a message is not bad though.


On Mon, 5 Feb 2001, S. Michael Denton wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Speaking as one with extensive experience with LVM on nearly every
> major unix vendor, it is not a -problem- but more of a lack of
> knowledge on the user/administrator's part.  As I recall, the
> documentation clearly notes that a filesystem that resides on an lv
> must be extended after extending the lv else the OS will not address
> the newly-allocated space.  IMHO it would be a -very- bad idea to
> automatically run ext2resize as not everyone uses ext2 on lvm and I
> think repeated offers to ask if you want to resize this ext2
> filesystem (that perhaps isn't even a filesystem at all) would get
> terribly annoying and NT-ish.  Also there's the issue with
> reduction... if you reduce an lv, LVM (linux LVM is not different
> than the other major unixes either) assumes that you have already
> reduced any filesystems, tablespaces, etc that might be using that
> space before you do the reduction.  Automatic reduction of a
> filesystem can be extraordinarily dangerous.
> 
> Perhaps as a compromise it could be a configuration flag in some lvm
> config file as to whether or not to automatically/offer to/never
> resize filesystems after extension/reduction.
> 
> Just a thought...
> 
> On Monday, 05 February 2001 07:25, James [SMTP:james@fr.clara.net]
> wrote:
> > 
> > That would be great :-)
> > 
> > On Mon, 5 Feb 2001, Tom Dawes-Gamble wrote:
> > 
> > > 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();}
> > > _______________________________________________
> > > linux-lvm mailing list
> > > linux-lvm@sistina.com
> > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > 
> > 
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> 
> 
> Scott Denton
> smdenton@bellsouth.net
> EFnet Handle: SteelWyng
> ICQ UIN: 24149258
> AIM Screen Name: SteelWyng
> 
> -----BEGIN PGP SIGNATURE-----
> Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
> 
> iQA/AwUBOn6ehnC+DNfF0nVpEQJHSACcCDGbtHNQW+j+4uNASe7YvM4aUUgAnjtb
> XiRAAN7W/5HQFuSbly6U3EK5
> =FTvP
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> 

RE: [linux-lvm] lv extend

[S. Michael Denton]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yes, printing the informative message may be a good idea as long as
it doesn't interfere with function (ie no 'hit enter to continue' or
anything like that). :)

On Monday, 05 February 2001 07:44, James [SMTP:james@fr.clara.net]
wrote:
> 
> Yes, I do have to agree. By reading the Doc I did quickly realize
> my error. The idea of printing a message is not bad though.
> 
> 
> On Mon, 5 Feb 2001, S. Michael Denton wrote:
> 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > Speaking as one with extensive experience with LVM on nearly
> > every major unix vendor, it is not a -problem- but more of a lack
> > of knowledge on the user/administrator's part.  As I recall, the
> > documentation clearly notes that a filesystem that resides on an
> > lv must be extended after extending the lv else the OS will not
> > address the newly-allocated space.  IMHO it would be a -very- bad
> > idea to automatically run ext2resize as not everyone uses ext2 on
> > lvm and I think repeated offers to ask if you want to resize this
> > ext2
> > filesystem (that perhaps isn't even a filesystem at all) would
> > get terribly annoying and NT-ish.  Also there's the issue with
> > reduction... if you reduce an lv, LVM (linux LVM is not different
> > than the other major unixes either) assumes that you have already
> > reduced any filesystems, tablespaces, etc that might be using
> > that space before you do the reduction.  Automatic reduction of a
> > filesystem can be extraordinarily dangerous.
> > 
> > Perhaps as a compromise it could be a configuration flag in some
> > lvm config file as to whether or not to automatically/offer
> > to/never resize filesystems after extension/reduction.
> > 
> > Just a thought...
> > 
> > On Monday, 05 February 2001 07:25, James
> > [SMTP:james@fr.clara.net] wrote:
> > > 
> > > That would be great :-)
> > > 
> > > On Mon, 5 Feb 2001, Tom Dawes-Gamble wrote:
> > > 
> > > > 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();}
> > > > _______________________________________________
> > > > linux-lvm mailing list
> > > > linux-lvm@sistina.com
> > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > 
> > > 
> > > _______________________________________________
> > > linux-lvm mailing list
> > > linux-lvm@sistina.com
> > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > 
> > 
> > Scott Denton
> > smdenton@bellsouth.net
> > EFnet Handle: SteelWyng
> > ICQ UIN: 24149258
> > AIM Screen Name: SteelWyng
> > 
> > -----BEGIN PGP SIGNATURE-----
> > Version: PGPfreeware 6.5.3 for non-commercial use
> > <http://www.pgp.com>  
> > 
> > iQA/AwUBOn6ehnC+DNfF0nVpEQJHSACcCDGbtHNQW+j+4uNASe7YvM4aUUgAnjtb
> > XiRAAN7W/5HQFuSbly6U3EK5
> > =FTvP
> > -----END PGP SIGNATURE-----
> > 
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm


Scott Denton
smdenton@bellsouth.net
EFnet Handle: SteelWyng
ICQ UIN: 24149258
AIM Screen Name: SteelWyng

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>

iQA/AwUBOn6gg3C+DNfF0nVpEQK4zQCgw4Tx/ckW6bCzRk3XzARNNffXOMwAnif3
fH0z5syYCyRz2m+/5QbJJe3j
=JGAT
-----END PGP SIGNATURE-----

RE: [linux-lvm] lv extend

[James]

It worked any way :-) Using e2fsadm. I succesfully resized my /home
But what about changing an important 'partition' like /usr ? Do I have to
do it with a rescue disk or something.


On Mon, 5 Feb 2001, S. Michael Denton wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Yes, printing the informative message may be a good idea as long as
> it doesn't interfere with function (ie no 'hit enter to continue' or
> anything like that). :)
> 
> On Monday, 05 February 2001 07:44, James [SMTP:james@fr.clara.net]
> wrote:
> > 
> > Yes, I do have to agree. By reading the Doc I did quickly realize
> > my error. The idea of printing a message is not bad though.
> > 
> > 
> > On Mon, 5 Feb 2001, S. Michael Denton wrote:
> > 
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > > 
> > > Speaking as one with extensive experience with LVM on nearly
> > > every major unix vendor, it is not a -problem- but more of a lack
> > > of knowledge on the user/administrator's part.  As I recall, the
> > > documentation clearly notes that a filesystem that resides on an
> > > lv must be extended after extending the lv else the OS will not
> > > address the newly-allocated space.  IMHO it would be a -very- bad
> > > idea to automatically run ext2resize as not everyone uses ext2 on
> > > lvm and I think repeated offers to ask if you want to resize this
> > > ext2
> > > filesystem (that perhaps isn't even a filesystem at all) would
> > > get terribly annoying and NT-ish.  Also there's the issue with
> > > reduction... if you reduce an lv, LVM (linux LVM is not different
> > > than the other major unixes either) assumes that you have already
> > > reduced any filesystems, tablespaces, etc that might be using
> > > that space before you do the reduction.  Automatic reduction of a
> > > filesystem can be extraordinarily dangerous.
> > > 
> > > Perhaps as a compromise it could be a configuration flag in some
> > > lvm config file as to whether or not to automatically/offer
> > > to/never resize filesystems after extension/reduction.
> > > 
> > > Just a thought...
> > > 
> > > On Monday, 05 February 2001 07:25, James
> > > [SMTP:james@fr.clara.net] wrote:
> > > > 
> > > > That would be great :-)
> > > > 
> > > > On Mon, 5 Feb 2001, Tom Dawes-Gamble wrote:
> > > > 
> > > > > 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();}
> > > > > _______________________________________________
> > > > > linux-lvm mailing list
> > > > > linux-lvm@sistina.com
> > > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > > 
> > > > 
> > > > _______________________________________________
> > > > linux-lvm mailing list
> > > > linux-lvm@sistina.com
> > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > 
> > > 
> > > Scott Denton
> > > smdenton@bellsouth.net
> > > EFnet Handle: SteelWyng
> > > ICQ UIN: 24149258
> > > AIM Screen Name: SteelWyng
> > > 
> > > -----BEGIN PGP SIGNATURE-----
> > > Version: PGPfreeware 6.5.3 for non-commercial use
> > > <http://www.pgp.com>  
> > > 
> > > iQA/AwUBOn6ehnC+DNfF0nVpEQJHSACcCDGbtHNQW+j+4uNASe7YvM4aUUgAnjtb
> > > XiRAAN7W/5HQFuSbly6U3EK5
> > > =FTvP
> > > -----END PGP SIGNATURE-----
> > > 
> > > _______________________________________________
> > > linux-lvm mailing list
> > > linux-lvm@sistina.com
> > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > 
> > 
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> 
> 
> Scott Denton
> smdenton@bellsouth.net
> EFnet Handle: SteelWyng
> ICQ UIN: 24149258
> AIM Screen Name: SteelWyng
> 
> -----BEGIN PGP SIGNATURE-----
> Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
> 
> iQA/AwUBOn6gg3C+DNfF0nVpEQK4zQCgw4Tx/ckW6bCzRk3XzARNNffXOMwAnif3
> fH0z5syYCyRz2m+/5QbJJe3j
> =JGAT
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> 

Re: [linux-lvm] lv extend

[Patrick Caulfield]

On Mon, Feb 05, 2001 at 07:45:55AM -0500, S. Michael Denton wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Yes, printing the informative message may be a good idea as long as
> it doesn't interfere with function (ie no 'hit enter to continue' or
> anything like that). :)
> 

Wouldn't it be better to use e2fsadm? That will ajust the filesystem and the LV
in the correct order depending on whether you are extending or reducing the LV.

The message is only a resonable idea for extending - if you are reducing the
message would e something like "I hope you remembered to reduce your
filesystem/tablespace first!"

patrick

Re: [linux-lvm] lv extend

[Jos Visser]

/usr is doable, because in single user mode you ought to be able to
umount /usr. Just make sure that your LVM tools are outside /usr (/sbin
would be a good idea).

Resizing the / file system would require considerable more work (rescue
system et cetera).

For the really brave, there are patches that allow online resizing of
partitions.

++Jos

And thus it came to pass that James wrote:
(on Mon, Feb 05, 2001 at 01:58:27PM +0100 to be exact)

> 
> It worked any way :-) Using e2fsadm. I succesfully resized my /home
> But what about changing an important 'partition' like /usr ? Do I have to
> do it with a rescue disk or something.
> 
> 
> On Mon, 5 Feb 2001, S. Michael Denton wrote:
> 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > Yes, printing the informative message may be a good idea as long as
> > it doesn't interfere with function (ie no 'hit enter to continue' or
> > anything like that). :)
> > 
> > On Monday, 05 February 2001 07:44, James [SMTP:james@fr.clara.net]
> > wrote:
> > > 
> > > Yes, I do have to agree. By reading the Doc I did quickly realize
> > > my error. The idea of printing a message is not bad though.
> > > 
> > > 
> > > On Mon, 5 Feb 2001, S. Michael Denton wrote:
> > > 
> > > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > Hash: SHA1
> > > > 
> > > > Speaking as one with extensive experience with LVM on nearly
> > > > every major unix vendor, it is not a -problem- but more of a lack
> > > > of knowledge on the user/administrator's part.  As I recall, the
> > > > documentation clearly notes that a filesystem that resides on an
> > > > lv must be extended after extending the lv else the OS will not
> > > > address the newly-allocated space.  IMHO it would be a -very- bad
> > > > idea to automatically run ext2resize as not everyone uses ext2 on
> > > > lvm and I think repeated offers to ask if you want to resize this
> > > > ext2
> > > > filesystem (that perhaps isn't even a filesystem at all) would
> > > > get terribly annoying and NT-ish.  Also there's the issue with
> > > > reduction... if you reduce an lv, LVM (linux LVM is not different
> > > > than the other major unixes either) assumes that you have already
> > > > reduced any filesystems, tablespaces, etc that might be using
> > > > that space before you do the reduction.  Automatic reduction of a
> > > > filesystem can be extraordinarily dangerous.
> > > > 
> > > > Perhaps as a compromise it could be a configuration flag in some
> > > > lvm config file as to whether or not to automatically/offer
> > > > to/never resize filesystems after extension/reduction.
> > > > 
> > > > Just a thought...
> > > > 
> > > > On Monday, 05 February 2001 07:25, James
> > > > [SMTP:james@fr.clara.net] wrote:
> > > > > 
> > > > > That would be great :-)
> > > > > 
> > > > > On Mon, 5 Feb 2001, Tom Dawes-Gamble wrote:
> > > > > 
> > > > > > 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();}
> > > > > > _______________________________________________
> > > > > > linux-lvm mailing list
> > > > > > linux-lvm@sistina.com
> > > > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > > > 
> > > > > 
> > > > > _______________________________________________
> > > > > linux-lvm mailing list
> > > > > linux-lvm@sistina.com
> > > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > 
> > > > 
> > > > Scott Denton
> > > > smdenton@bellsouth.net
> > > > EFnet Handle: SteelWyng
> > > > ICQ UIN: 24149258
> > > > AIM Screen Name: SteelWyng
> > > > 
> > > > -----BEGIN PGP SIGNATURE-----
> > > > Version: PGPfreeware 6.5.3 for non-commercial use
> > > > <http://www.pgp.com>  
> > > > 
> > > > iQA/AwUBOn6ehnC+DNfF0nVpEQJHSACcCDGbtHNQW+j+4uNASe7YvM4aUUgAnjtb
> > > > XiRAAN7W/5HQFuSbly6U3EK5
> > > > =FTvP
> > > > -----END PGP SIGNATURE-----
> > > > 
> > > > _______________________________________________
> > > > linux-lvm mailing list
> > > > linux-lvm@sistina.com
> > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > 
> > > 
> > > _______________________________________________
> > > linux-lvm mailing list
> > > linux-lvm@sistina.com
> > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > 
> > 
> > Scott Denton
> > smdenton@bellsouth.net
> > EFnet Handle: SteelWyng
> > ICQ UIN: 24149258
> > AIM Screen Name: SteelWyng
> > 
> > -----BEGIN PGP SIGNATURE-----
> > Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
> > 
> > iQA/AwUBOn6gg3C+DNfF0nVpEQK4zQCgw4Tx/ckW6bCzRk3XzARNNffXOMwAnif3
> > fH0z5syYCyRz2m+/5QbJJe3j
> > =JGAT
> > -----END PGP SIGNATURE-----
> > 
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm

-- 
I have no need for a spirituality which can not encompass my humanness.

Re: [linux-lvm] lv extend

[James]

Hmmm... Sorry to be daft but I'm having trouble doing the /usr

I boot into single

umount /usr (its on /dev/lvdev/usr)
Then I do e2fsadm /dev/lvdev/usr -L+500M

I get the message "succesfully extended" etc but also

resize2fs 1.19
please run e2fsck -f /dev/lvdev/usr first.

Needles to say a 

munster:/home/james# df -h  
Filesystem            Size  Used Avail Use% Mounted on
/dev/hda1             4.6G  1.9G  2.4G  44% /
/dev/lvdev/home       1.4G  322M  1.0G  23% /home
/dev/lvdev/var        984M   93M  842M  10% /var
/dev/lvdev/usr        984M  485M  450M  52% /usr

Dosen't show the size increase. But a vgdisplay -v does show it(It shows
that I have tried twice :-)

--- Logical volume ---
LV Name                /dev/lvdev/usr
VG Name                lvdev
LV Write Access        read/write
LV Status              available
LV #                   2
# open                 1
LV Size                2.93 GB
Current LE             750
Allocated LE           750
Allocation             next free
Read ahead sectors     120
Block device           58:1

What is strange is that the same manip worked perfectly for /home 
What am I missing?

cheers

On Mon, 5 Feb 2001, Jos Visser wrote:

> /usr is doable, because in single user mode you ought to be able to
> umount /usr. Just make sure that your LVM tools are outside /usr (/sbin
> would be a good idea).
> 
> Resizing the / file system would require considerable more work (rescue
> system et cetera).
> 
> For the really brave, there are patches that allow online resizing of
> partitions.
> 
> ++Jos
> 
> And thus it came to pass that James wrote:
> (on Mon, Feb 05, 2001 at 01:58:27PM +0100 to be exact)
> 
> > 
> > It worked any way :-) Using e2fsadm. I succesfully resized my /home
> > But what about changing an important 'partition' like /usr ? Do I have to
> > do it with a rescue disk or something.
> > 
> > 
> > On Mon, 5 Feb 2001, S. Michael Denton wrote:
> > 
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > > 
> > > Yes, printing the informative message may be a good idea as long as
> > > it doesn't interfere with function (ie no 'hit enter to continue' or
> > > anything like that). :)
> > > 
> > > On Monday, 05 February 2001 07:44, James [SMTP:james@fr.clara.net]
> > > wrote:
> > > > 
> > > > Yes, I do have to agree. By reading the Doc I did quickly realize
> > > > my error. The idea of printing a message is not bad though.
> > > > 
> > > > 
> > > > On Mon, 5 Feb 2001, S. Michael Denton wrote:
> > > > 
> > > > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > > Hash: SHA1
> > > > > 
> > > > > Speaking as one with extensive experience with LVM on nearly
> > > > > every major unix vendor, it is not a -problem- but more of a lack
> > > > > of knowledge on the user/administrator's part.  As I recall, the
> > > > > documentation clearly notes that a filesystem that resides on an
> > > > > lv must be extended after extending the lv else the OS will not
> > > > > address the newly-allocated space.  IMHO it would be a -very- bad
> > > > > idea to automatically run ext2resize as not everyone uses ext2 on
> > > > > lvm and I think repeated offers to ask if you want to resize this
> > > > > ext2
> > > > > filesystem (that perhaps isn't even a filesystem at all) would
> > > > > get terribly annoying and NT-ish.  Also there's the issue with
> > > > > reduction... if you reduce an lv, LVM (linux LVM is not different
> > > > > than the other major unixes either) assumes that you have already
> > > > > reduced any filesystems, tablespaces, etc that might be using
> > > > > that space before you do the reduction.  Automatic reduction of a
> > > > > filesystem can be extraordinarily dangerous.
> > > > > 
> > > > > Perhaps as a compromise it could be a configuration flag in some
> > > > > lvm config file as to whether or not to automatically/offer
> > > > > to/never resize filesystems after extension/reduction.
> > > > > 
> > > > > Just a thought...
> > > > > 
> > > > > On Monday, 05 February 2001 07:25, James
> > > > > [SMTP:james@fr.clara.net] wrote:
> > > > > > 
> > > > > > That would be great :-)
> > > > > > 
> > > > > > On Mon, 5 Feb 2001, Tom Dawes-Gamble wrote:
> > > > > > 
> > > > > > > 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();}
> > > > > > > _______________________________________________
> > > > > > > linux-lvm mailing list
> > > > > > > linux-lvm@sistina.com
> > > > > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > > > > 
> > > > > > 
> > > > > > _______________________________________________
> > > > > > linux-lvm mailing list
> > > > > > linux-lvm@sistina.com
> > > > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > > 
> > > > > 
> > > > > Scott Denton
> > > > > smdenton@bellsouth.net
> > > > > EFnet Handle: SteelWyng
> > > > > ICQ UIN: 24149258
> > > > > AIM Screen Name: SteelWyng
> > > > > 
> > > > > -----BEGIN PGP SIGNATURE-----
> > > > > Version: PGPfreeware 6.5.3 for non-commercial use
> > > > > <http://www.pgp.com>  
> > > > > 
> > > > > iQA/AwUBOn6ehnC+DNfF0nVpEQJHSACcCDGbtHNQW+j+4uNASe7YvM4aUUgAnjtb
> > > > > XiRAAN7W/5HQFuSbly6U3EK5
> > > > > =FTvP
> > > > > -----END PGP SIGNATURE-----
> > > > > 
> > > > > _______________________________________________
> > > > > linux-lvm mailing list
> > > > > linux-lvm@sistina.com
> > > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > > 
> > > > 
> > > > _______________________________________________
> > > > linux-lvm mailing list
> > > > linux-lvm@sistina.com
> > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > 
> > > 
> > > Scott Denton
> > > smdenton@bellsouth.net
> > > EFnet Handle: SteelWyng
> > > ICQ UIN: 24149258
> > > AIM Screen Name: SteelWyng
> > > 
> > > -----BEGIN PGP SIGNATURE-----
> > > Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
> > > 
> > > iQA/AwUBOn6gg3C+DNfF0nVpEQK4zQCgw4Tx/ckW6bCzRk3XzARNNffXOMwAnif3
> > > fH0z5syYCyRz2m+/5QbJJe3j
> > > =JGAT
> > > -----END PGP SIGNATURE-----
> > > 
> > > _______________________________________________
> > > linux-lvm mailing list
> > > linux-lvm@sistina.com
> > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > 
> > 
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> 
> -- 
> I have no need for a spirituality which can not encompass my humanness.
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> 

Re: [linux-lvm] lv extend

[Jos Visser]

Why not:

- go into single user mode
- umount /usr
- e2fsck -f /dev/lvdev/usr
- run resize2fs manually
- mount /usr
- df -h /usr

++Jos

And thus it came to pass that James wrote:
(on Mon, Feb 05, 2001 at 03:10:19PM +0100 to be exact)

> 
> Hmmm... Sorry to be daft but I'm having trouble doing the /usr
> 
> I boot into single
> 
> umount /usr (its on /dev/lvdev/usr)
> Then I do e2fsadm /dev/lvdev/usr -L+500M
> 
> I get the message "succesfully extended" etc but also
> 
> resize2fs 1.19
> please run e2fsck -f /dev/lvdev/usr first.
> 
> Needles to say a 
> 
> munster:/home/james# df -h  
> Filesystem            Size  Used Avail Use% Mounted on
> /dev/hda1             4.6G  1.9G  2.4G  44% /
> /dev/lvdev/home       1.4G  322M  1.0G  23% /home
> /dev/lvdev/var        984M   93M  842M  10% /var
> /dev/lvdev/usr        984M  485M  450M  52% /usr
> 
> Dosen't show the size increase. But a vgdisplay -v does show it(It shows
> that I have tried twice :-)
> 
> --- Logical volume ---
> LV Name                /dev/lvdev/usr
> VG Name                lvdev
> LV Write Access        read/write
> LV Status              available
> LV #                   2
> # open                 1
> LV Size                2.93 GB
> Current LE             750
> Allocated LE           750
> Allocation             next free
> Read ahead sectors     120
> Block device           58:1
> 
> What is strange is that the same manip worked perfectly for /home 
> What am I missing?
> 
> cheers
> 
> On Mon, 5 Feb 2001, Jos Visser wrote:
> 
> > /usr is doable, because in single user mode you ought to be able to
> > umount /usr. Just make sure that your LVM tools are outside /usr (/sbin
> > would be a good idea).
> > 
> > Resizing the / file system would require considerable more work (rescue
> > system et cetera).
> > 
> > For the really brave, there are patches that allow online resizing of
> > partitions.
> > 
> > ++Jos
> > 
> > And thus it came to pass that James wrote:
> > (on Mon, Feb 05, 2001 at 01:58:27PM +0100 to be exact)
> > 
> > > 
> > > It worked any way :-) Using e2fsadm. I succesfully resized my /home
> > > But what about changing an important 'partition' like /usr ? Do I have to
> > > do it with a rescue disk or something.
> > > 
> > > 
> > > On Mon, 5 Feb 2001, S. Michael Denton wrote:
> > > 
> > > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > Hash: SHA1
> > > > 
> > > > Yes, printing the informative message may be a good idea as long as
> > > > it doesn't interfere with function (ie no 'hit enter to continue' or
> > > > anything like that). :)
> > > > 
> > > > On Monday, 05 February 2001 07:44, James [SMTP:james@fr.clara.net]
> > > > wrote:
> > > > > 
> > > > > Yes, I do have to agree. By reading the Doc I did quickly realize
> > > > > my error. The idea of printing a message is not bad though.
> > > > > 
> > > > > 
> > > > > On Mon, 5 Feb 2001, S. Michael Denton wrote:
> > > > > 
> > > > > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > > > Hash: SHA1
> > > > > > 
> > > > > > Speaking as one with extensive experience with LVM on nearly
> > > > > > every major unix vendor, it is not a -problem- but more of a lack
> > > > > > of knowledge on the user/administrator's part.  As I recall, the
> > > > > > documentation clearly notes that a filesystem that resides on an
> > > > > > lv must be extended after extending the lv else the OS will not
> > > > > > address the newly-allocated space.  IMHO it would be a -very- bad
> > > > > > idea to automatically run ext2resize as not everyone uses ext2 on
> > > > > > lvm and I think repeated offers to ask if you want to resize this
> > > > > > ext2
> > > > > > filesystem (that perhaps isn't even a filesystem at all) would
> > > > > > get terribly annoying and NT-ish.  Also there's the issue with
> > > > > > reduction... if you reduce an lv, LVM (linux LVM is not different
> > > > > > than the other major unixes either) assumes that you have already
> > > > > > reduced any filesystems, tablespaces, etc that might be using
> > > > > > that space before you do the reduction.  Automatic reduction of a
> > > > > > filesystem can be extraordinarily dangerous.
> > > > > > 
> > > > > > Perhaps as a compromise it could be a configuration flag in some
> > > > > > lvm config file as to whether or not to automatically/offer
> > > > > > to/never resize filesystems after extension/reduction.
> > > > > > 
> > > > > > Just a thought...
> > > > > > 
> > > > > > On Monday, 05 February 2001 07:25, James
> > > > > > [SMTP:james@fr.clara.net] wrote:
> > > > > > > 
> > > > > > > That would be great :-)
> > > > > > > 
> > > > > > > On Mon, 5 Feb 2001, Tom Dawes-Gamble wrote:
> > > > > > > 
> > > > > > > > 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();}
> > > > > > > > _______________________________________________
> > > > > > > > linux-lvm mailing list
> > > > > > > > linux-lvm@sistina.com
> > > > > > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > > > > > 
> > > > > > > 
> > > > > > > _______________________________________________
> > > > > > > linux-lvm mailing list
> > > > > > > linux-lvm@sistina.com
> > > > > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > > > 
> > > > > > 
> > > > > > Scott Denton
> > > > > > smdenton@bellsouth.net
> > > > > > EFnet Handle: SteelWyng
> > > > > > ICQ UIN: 24149258
> > > > > > AIM Screen Name: SteelWyng
> > > > > > 
> > > > > > -----BEGIN PGP SIGNATURE-----
> > > > > > Version: PGPfreeware 6.5.3 for non-commercial use
> > > > > > <http://www.pgp.com>  
> > > > > > 
> > > > > > iQA/AwUBOn6ehnC+DNfF0nVpEQJHSACcCDGbtHNQW+j+4uNASe7YvM4aUUgAnjtb
> > > > > > XiRAAN7W/5HQFuSbly6U3EK5
> > > > > > =FTvP
> > > > > > -----END PGP SIGNATURE-----
> > > > > > 
> > > > > > _______________________________________________
> > > > > > linux-lvm mailing list
> > > > > > linux-lvm@sistina.com
> > > > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > > > 
> > > > > 
> > > > > _______________________________________________
> > > > > linux-lvm mailing list
> > > > > linux-lvm@sistina.com
> > > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > 
> > > > 
> > > > Scott Denton
> > > > smdenton@bellsouth.net
> > > > EFnet Handle: SteelWyng
> > > > ICQ UIN: 24149258
> > > > AIM Screen Name: SteelWyng
> > > > 
> > > > -----BEGIN PGP SIGNATURE-----
> > > > Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
> > > > 
> > > > iQA/AwUBOn6gg3C+DNfF0nVpEQK4zQCgw4Tx/ckW6bCzRk3XzARNNffXOMwAnif3
> > > > fH0z5syYCyRz2m+/5QbJJe3j
> > > > =JGAT
> > > > -----END PGP SIGNATURE-----
> > > > 
> > > > _______________________________________________
> > > > linux-lvm mailing list
> > > > linux-lvm@sistina.com
> > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > 
> > > 
> > > _______________________________________________
> > > linux-lvm mailing list
> > > linux-lvm@sistina.com
> > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > 
> > -- 
> > I have no need for a spirituality which can not encompass my humanness.
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm

-- 
I have no need for a spirituality which can not encompass my humanness.

Re: [linux-lvm] lv extend

[Richard Smith]

dmeyer@dmeyer.net wrote:
> 
> In article <Pine.LNX.4.21.0102051355290.698-100000@munster.noc.fr.clara.net> you write:
> >
> > It worked any way :-) Using e2fsadm. I succesfully resized my /home
> > But what about changing an important 'partition' like /usr ? Do I have to
> > do it with a rescue disk or something.
> 
> FYI, reiserfs apparently allows resizing of a mounted filesystem.
> Mind you, I'd do a backup before trying anything resembling that, but
> then backing up before resizing is always a good idea.
> 
> --
> Dave Meyer
> dmeyer@dmeyer.net
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm

Do you have anymore information on this.  I use reiser on my LV now.
Its just scratch disks so I can play.  I am intrested in this chfs
issue.

Re: [linux-lvm] lv extend

[James]

It worked ! (sorry to sound so surprised :-)

The resize2fs -f had me stuck for a while :-)

Thanks for your help

James 

On Mon, 5 Feb 2001, Jos Visser wrote:

> Why not:
> 
> - go into single user mode
> - umount /usr
> - e2fsck -f /dev/lvdev/usr
> - run resize2fs manually
> - mount /usr
> - df -h /usr
> 
> ++Jos
> 
> And thus it came to pass that James wrote:
> (on Mon, Feb 05, 2001 at 03:10:19PM +0100 to be exact)
> 
> > 
> > Hmmm... Sorry to be daft but I'm having trouble doing the /usr
> > 
> > I boot into single
> > 
> > umount /usr (its on /dev/lvdev/usr)
> > Then I do e2fsadm /dev/lvdev/usr -L+500M
> > 
> > I get the message "succesfully extended" etc but also
> > 
> > resize2fs 1.19
> > please run e2fsck -f /dev/lvdev/usr first.
> > 
> > Needles to say a 
> > 
> > munster:/home/james# df -h  
> > Filesystem            Size  Used Avail Use% Mounted on
> > /dev/hda1             4.6G  1.9G  2.4G  44% /
> > /dev/lvdev/home       1.4G  322M  1.0G  23% /home
> > /dev/lvdev/var        984M   93M  842M  10% /var
> > /dev/lvdev/usr        984M  485M  450M  52% /usr
> > 
> > Dosen't show the size increase. But a vgdisplay -v does show it(It shows
> > that I have tried twice :-)
> > 
> > --- Logical volume ---
> > LV Name                /dev/lvdev/usr
> > VG Name                lvdev
> > LV Write Access        read/write
> > LV Status              available
> > LV #                   2
> > # open                 1
> > LV Size                2.93 GB
> > Current LE             750
> > Allocated LE           750
> > Allocation             next free
> > Read ahead sectors     120
> > Block device           58:1
> > 
> > What is strange is that the same manip worked perfectly for /home 
> > What am I missing?
> > 
> > cheers
> > 
> > On Mon, 5 Feb 2001, Jos Visser wrote:
> > 
> > > /usr is doable, because in single user mode you ought to be able to
> > > umount /usr. Just make sure that your LVM tools are outside /usr (/sbin
> > > would be a good idea).
> > > 
> > > Resizing the / file system would require considerable more work (rescue
> > > system et cetera).
> > > 
> > > For the really brave, there are patches that allow online resizing of
> > > partitions.
> > > 
> > > ++Jos
> > > 
> > > And thus it came to pass that James wrote:
> > > (on Mon, Feb 05, 2001 at 01:58:27PM +0100 to be exact)
> > > 
> > > > 
> > > > It worked any way :-) Using e2fsadm. I succesfully resized my /home
> > > > But what about changing an important 'partition' like /usr ? Do I have to
> > > > do it with a rescue disk or something.
> > > > 
> > > > 
> > > > On Mon, 5 Feb 2001, S. Michael Denton wrote:
> > > > 
> > > > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > > Hash: SHA1
> > > > > 
> > > > > Yes, printing the informative message may be a good idea as long as
> > > > > it doesn't interfere with function (ie no 'hit enter to continue' or
> > > > > anything like that). :)
> > > > > 
> > > > > On Monday, 05 February 2001 07:44, James [SMTP:james@fr.clara.net]
> > > > > wrote:
> > > > > > 
> > > > > > Yes, I do have to agree. By reading the Doc I did quickly realize
> > > > > > my error. The idea of printing a message is not bad though.
> > > > > > 
> > > > > > 
> > > > > > On Mon, 5 Feb 2001, S. Michael Denton wrote:
> > > > > > 
> > > > > > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > > > > Hash: SHA1
> > > > > > > 
> > > > > > > Speaking as one with extensive experience with LVM on nearly
> > > > > > > every major unix vendor, it is not a -problem- but more of a lack
> > > > > > > of knowledge on the user/administrator's part.  As I recall, the
> > > > > > > documentation clearly notes that a filesystem that resides on an
> > > > > > > lv must be extended after extending the lv else the OS will not
> > > > > > > address the newly-allocated space.  IMHO it would be a -very- bad
> > > > > > > idea to automatically run ext2resize as not everyone uses ext2 on
> > > > > > > lvm and I think repeated offers to ask if you want to resize this
> > > > > > > ext2
> > > > > > > filesystem (that perhaps isn't even a filesystem at all) would
> > > > > > > get terribly annoying and NT-ish.  Also there's the issue with
> > > > > > > reduction... if you reduce an lv, LVM (linux LVM is not different
> > > > > > > than the other major unixes either) assumes that you have already
> > > > > > > reduced any filesystems, tablespaces, etc that might be using
> > > > > > > that space before you do the reduction.  Automatic reduction of a
> > > > > > > filesystem can be extraordinarily dangerous.
> > > > > > > 
> > > > > > > Perhaps as a compromise it could be a configuration flag in some
> > > > > > > lvm config file as to whether or not to automatically/offer
> > > > > > > to/never resize filesystems after extension/reduction.
> > > > > > > 
> > > > > > > Just a thought...
> > > > > > > 
> > > > > > > On Monday, 05 February 2001 07:25, James
> > > > > > > [SMTP:james@fr.clara.net] wrote:
> > > > > > > > 
> > > > > > > > That would be great :-)
> > > > > > > > 
> > > > > > > > On Mon, 5 Feb 2001, Tom Dawes-Gamble wrote:
> > > > > > > > 
> > > > > > > > > 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();}
> > > > > > > > > _______________________________________________
> > > > > > > > > linux-lvm mailing list
> > > > > > > > > linux-lvm@sistina.com
> > > > > > > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > > > > > > 
> > > > > > > > 
> > > > > > > > _______________________________________________
> > > > > > > > linux-lvm mailing list
> > > > > > > > linux-lvm@sistina.com
> > > > > > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > > > > 
> > > > > > > 
> > > > > > > Scott Denton
> > > > > > > smdenton@bellsouth.net
> > > > > > > EFnet Handle: SteelWyng
> > > > > > > ICQ UIN: 24149258
> > > > > > > AIM Screen Name: SteelWyng
> > > > > > > 
> > > > > > > -----BEGIN PGP SIGNATURE-----
> > > > > > > Version: PGPfreeware 6.5.3 for non-commercial use
> > > > > > > <http://www.pgp.com>  
> > > > > > > 
> > > > > > > iQA/AwUBOn6ehnC+DNfF0nVpEQJHSACcCDGbtHNQW+j+4uNASe7YvM4aUUgAnjtb
> > > > > > > XiRAAN7W/5HQFuSbly6U3EK5
> > > > > > > =FTvP
> > > > > > > -----END PGP SIGNATURE-----
> > > > > > > 
> > > > > > > _______________________________________________
> > > > > > > linux-lvm mailing list
> > > > > > > linux-lvm@sistina.com
> > > > > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > > > > 
> > > > > > 
> > > > > > _______________________________________________
> > > > > > linux-lvm mailing list
> > > > > > linux-lvm@sistina.com
> > > > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > > 
> > > > > 
> > > > > Scott Denton
> > > > > smdenton@bellsouth.net
> > > > > EFnet Handle: SteelWyng
> > > > > ICQ UIN: 24149258
> > > > > AIM Screen Name: SteelWyng
> > > > > 
> > > > > -----BEGIN PGP SIGNATURE-----
> > > > > Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
> > > > > 
> > > > > iQA/AwUBOn6gg3C+DNfF0nVpEQK4zQCgw4Tx/ckW6bCzRk3XzARNNffXOMwAnif3
> > > > > fH0z5syYCyRz2m+/5QbJJe3j
> > > > > =JGAT
> > > > > -----END PGP SIGNATURE-----
> > > > > 
> > > > > _______________________________________________
> > > > > linux-lvm mailing list
> > > > > linux-lvm@sistina.com
> > > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > > > 
> > > > 
> > > > _______________________________________________
> > > > linux-lvm mailing list
> > > > linux-lvm@sistina.com
> > > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > 
> > > -- 
> > > I have no need for a spirituality which can not encompass my humanness.
> > > _______________________________________________
> > > linux-lvm mailing list
> > > linux-lvm@sistina.com
> > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > > 
> > 
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> 
> -- 
> I have no need for a spirituality which can not encompass my humanness.
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> 

Re: [linux-lvm] lv extend

[Richard Smith]

--snip--
thanks for the tip.  I will try it out.
with some junk data.

Re: [linux-lvm] lv extend

[Tom Dawes-Gamble]

Hi,

Having looked at what e2fsadm(8) can do it's not really required
to make the changes I suggested.  I had a go at stupid things like
reduceing the lvol below the minimum size need for the file system
(which failed and left the lvol untouched. exactly like it should!)

I think I would favour adding [-A y/n] to e2fsadm and promote the use of 
e2fsadm for resizing ext2 file systems.  That said I don't really favour
the use of -A well not unless you are doing hundereds of operations on
the vg in one go.

Regards,
Tom.



> 
> 
> That would be great :-)
> 
> On Mon, 5 Feb 2001, Tom Dawes-Gamble wrote:
> 
> > Hi,
> >=20
> > =09This 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.
> >=20
> > =09Perhaps a message like.
> >=20
> > [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
> >=20
> > Note:  You need to run a resize utility such as ext2resize before
> > =09the space is available in the file system.
> >=20
> > [root@localhost /root]#
> >=20
> > 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.
> >=20
> > Regards,
> > Tom.
> >=20
> > >=20
> > > James wrote:
> > > >=20
> > > > Hello
> > > >=20
> > > > Is it normal after growing an LV not to see the change with df -h ? B=
> ut 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.
> > >=20
> > > Bye...
> > >=20
> > > =09Dirk
> > > --=20
> > > Dirk Heinrichs=09=09| Tel:=09+49 (0)241 413 260
> > > QIS Systemhaus GmbH=09| Fax:=09+49 (0)241 413 2640
> > > J=FClicher Str. 338b=09| Mail:=09heinrichs@qis-systemhaus.de
> > > D-52070 Aachen=09=09| Web:=09http://www.qis-systemhaus.de
> > > _______________________________________________
> > > linux-lvm mailing list
> > > linux-lvm@sistina.com
> > > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > >=20
> >=20
> >=20
> > --
> >  int/* PROCEDURE DIVISION.*>*/b,g,l,n=3D'/'/'/'<<2;extern void printf();i=
> nt main
> >  (int d,char**z){char*o,*c=3D"%.9s%.7s%.7s\n";l=3D*(c+d+d)-*(c+d);g=3D*c-=
> d-l;b=3Dl+n++;
> >    o=3D"  DISPLAY'tmdg@uksr'    '.hp.com' *>"+g++;printf(c,o-b++,o+l,o);l=
> =3D~++n;
> >    o=3D"  DISPLAY'http://www.itrc.hp.com/' *>"+g++;printf(c,o-b++,o+l,o);=
> exit();}
> > _______________________________________________
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> >=20
> 
> _______________________________________________
> 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();}

Re: [linux-lvm] lv extend

[dmeyer]

In article <Pine.LNX.4.21.0102051355290.698-100000@munster.noc.fr.clara.net> you write:
> 
> It worked any way :-) Using e2fsadm. I succesfully resized my /home
> But what about changing an important 'partition' like /usr ? Do I have to
> do it with a rescue disk or something.

FYI, reiserfs apparently allows resizing of a mounted filesystem.
Mind you, I'd do a backup before trying anything resembling that, but
then backing up before resizing is always a good idea.

-- 
Dave Meyer
dmeyer@dmeyer.net

Re: [linux-lvm] lv extend

[Erik Bågfors]

On 05 Feb 2001 14:34:45 -0500,  wrote:
> In article <Pine.LNX.4.21.0102051355290.698-100000@munster.noc.fr.clara.net> you write:
> > 
> > It worked any way :-) Using e2fsadm. I succesfully resized my /home
> > But what about changing an important 'partition' like /usr ? Do I have to
> > do it with a rescue disk or something.
> 
> FYI, reiserfs apparently allows resizing of a mounted filesystem.
> Mind you, I'd do a backup before trying anything resembling that, but
> then backing up before resizing is always a good idea.
> 


I have resized reiserfs online alot.  I have never had any problems with
it.  Am at the point 
where I don't do backups at all because everything just works so good.  

Ofcourse.. I live alittle bit dangerous when doing that I know...

/Erik

-- 
Erik Bågfors               | http://erik.bagfors.nu/    
erik@bagfors.nu            | Erik.Bagfors@engohol.se
Supporter of free software | GSM +46 733 279 273
fingerprint: 6666 A85B 95D3 D26B 296B 6C60 4F32 2C0B 693D 6E32

Re: [linux-lvm] lv extend

[dmeyer]

In article <3A7EBEE6.14490D5F@tampabay.rr.com> you write:
> dmeyer@dmeyer.net wrote:
> > FYI, reiserfs apparently allows resizing of a mounted filesystem.
> > Mind you, I'd do a backup before trying anything resembling that, but
> > then backing up before resizing is always a good idea.
> 
> Do you have anymore information on this.  I use reiser on my LV now.
> Its just scratch disks so I can play.  I am intrested in this chfs
> issue.

It's pretty easy.  Use lvextend to increase the size of the LV, then
run something like resize_reiserfs -f /dev/misc_vg/am_lv, and it'll
just work.  By default resize_reiserfs expands the filesystem to fill
the LV, but you can specify how much to grow the filesystem with -s.

This doesn't work, BTW, for shrinking.  You must unmount the
filesystem to shrink it, then use lvreduce to shrink the LV.

-- 
Dave Meyer
dmeyer@dmeyer.net

Re: [linux-lvm] lv extend

[Andreas Dilger]

Jos Visser writes:
> Resizing the / file system would require considerable more work (rescue
> system et cetera).
> 
> For the really brave, there are patches that allow online resizing of
> partitions.

Not to be overly positive or anything, but the online ext2 resizing is
actually very safe.  With the exception of the fact the user tools don't
work on big-endian systems, I haven't had any bug reports on this in a
long time.  Even then, I've basically never had a bug report that ended
in data loss.

The only issue with online ext2 resizing is that changes in the latest
2.4 kernels cause an oops at resize time.  This has been fixed, and I
will probably be releasing a new ext2resize tools, mostly to update the
kernel patches.

On Mon, 5 Feb 2001, Tom Dawes-Gamble wrote:
> 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.

That's what e2fsadm is for - it will resize the filesystem and the
LV at the same time.  IMHO, it is a bad idea to make lvextend do
filesystem work.  However, for some reason the 0.9 version of e2fsadm
doesn't have the online resizing changes that are in 0.8.1.  I have a
patch to fix this.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert