From: "S. Michael Denton" <smdenton@bellsouth.net>
To: "'linux-lvm@sistina.com'" <linux-lvm@sistina.com>
Subject: RE: [linux-lvm] lv extend
Date: Mon, 5 Feb 2001 07:45:55 -0500 [thread overview]
Message-ID: <01C08F47.ADAB2B60.smdenton@bellsouth.net> (raw)
-----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-----
next reply other threads:[~2001-02-05 12:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 12:45 S. Michael Denton [this message]
2001-02-05 12:58 ` [linux-lvm] lv extend 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
-- 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 11:16 James
2001-02-05 11:52 ` Dirk Heinrichs
2001-02-05 12:11 ` Tom Dawes-Gamble
2001-02-05 12:24 ` James
2001-02-05 18:01 ` Tom Dawes-Gamble
2001-02-05 12:13 ` James
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=01C08F47.ADAB2B60.smdenton@bellsouth.net \
--to=smdenton@bellsouth.net \
--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 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.