From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM Questions
Date: Fri, 4 May 2001 09:33:50 +0000 [thread overview]
Message-ID: <20010504093350.D4700@sistina.com> (raw)
In-Reply-To: <wv4rv26hvj.fsf@freeze.oslo.dnmi.no>; from a.phillips@dnmi.no on Thu, May 03, 2001 at 08:56:00AM +0200
On Thu, May 03, 2001 at 08:56:00AM +0200, Adrian Phillips wrote:
> >>>>> "Evan" == Evan Day <banal@home.com> writes:
>
> <snip>
>
> >> What ext2 resize utility is the ideal choice for LVM to
> >> use. parted seems to be quite functional, but having to down
> >> the machine to single is a but annoying. Has anyone
> >> successfully used the ext2online utility on RedHat? It seems as
> >> though the version of e2fsprogs that includes this code is part
> >> of RH 7.1 anyways. At least from what I can tell. The online
> >> resizing would definitely be required for a highly available
> >> system as well.
>
> Evan> I don't have much experience with ext2 resizing, but the
>
> I haven't either.
>
> Evan> reiserfs can easily be extended. I'm not sure if it is
> Evan> supported or not, but I've actually extended filesystems
> Evan> while mounted with no ill effects.
>
> I believe it is officially supported, ie. if it breaks then its a bug,
> and have done it now several times, at least on lightly loaded
> filesystems. Its not quite as convienient as AIX's LVM, in that one
> resizes the filesystem and the logical volume is automatically
> resized, but if I'm bothered I'll write a wrapper script around
> lvextend/lvreduce for that.
>
> A question for the developers if they notice. Why lvextend and
> lvreduce, as they do the same things. Is it just for clarity ? A
> lvresize with + or - or a fixed size to could the same ?
The Linux LVM CLI is as close as possible to the HP/UX one which has
those commands (and vgextend/vgreduce as well) seperate.
This makes at least me as a long term HP/UX LVM user happy ;-)
lvresize can easily be made as a convenence wrapper though...
>
> <snip>
>
> >> I also read an older thread on an X11 GUI as well as some
> >> replies to it. The GUI that comes with Veritas is completely
> >> useless and the command line tools are completely
> >> over-engineered. While it would be nice for a small company
> >> trying to save money not to call in a specialist to create
> >> VG's, it certainly wouldn't be a requirement. Get everything
> >> stable, reliable and consistent than someone will probably have
> >> the time to create the GUI. I'd dedicate time to that type of
> >> project, but why bother when the code isn't quite there
> >> yet. There's no reason.
>
> Evan> LVM is so simple that, IMHO, a GUI shouldn't be an
> Evan> overriding concern. Then again, I've been working with LVM
> Evan> on HP-UX for many years, and I find the CLI utilities to be
> Evan> much more efficient than waiting for SAM (the HP-UX sysadmin
> Evan> GUI) to poll everything, build displays, etc. The current
> Evan> CLI tools are lean and aligned with the LVM model in a way
> Evan> that is both logical and easy to understand.
>
> On the web page there is a BETA lva, written in perl-tk which works
> nicely although somewhat limited currently. I like the pie chart look,
> not for me personally, CLI type myself, but for some of the others at
> work who must have a GUI for everything, yukk :-)
>
> Sincerely,
>
> Adrian Phillips
>
> --
> Your mouse has moved.
> Windows NT must be restarted for the change to take effect.
> Reboot now? [OK]
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
--
Regards,
Heinz -- The LVM Guy --
*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-05-04 9:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-03 0:48 [linux-lvm] LVM Questions Darren Young
2001-05-03 1:26 ` Glenn Shannon
2001-05-03 1:45 ` Evan Day
2001-05-03 6:56 ` Adrian Phillips
2001-05-04 9:33 ` Heinz J. Mauelshagen [this message]
2001-05-04 7:45 ` Adrian Phillips
2001-05-04 10:38 ` Heinz J. Mauelshagen
2001-05-04 9:38 ` Adrian Phillips
2001-05-04 13:39 ` Heinz J. Mauelshagen
2001-05-08 7:38 ` [linux-lvm] (no subject) Merence Sibomana
2001-05-03 11:15 ` [linux-lvm] LVM Questions Heinz J. Mauelshagen
2001-05-03 11:41 ` Carlo Marcelo Arenas Belon
2001-05-04 1:59 ` Mark van Walraven
-- strict thread matches above, loose matches on Subject: below --
2007-03-29 16:55 [linux-lvm] LVM questions Eric A. Hall
2007-03-29 17:38 ` Stuart D. Gathman
2007-04-20 13:36 ` Nix
2008-03-27 22:27 [linux-lvm] LVM Questions Nicholas Muguira
2008-04-02 8:20 ` Jordi Prats
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=20010504093350.D4700@sistina.com \
--to=mauelshagen@sistina.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).