linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Mats Wichmann <mats@laplaza.org>
To: linux-lvm@msede.com
Subject: Re: [linux-lvm] LVM in stock kernel!?
Date: Thu, 26 Aug 1999 12:30:21 -0600	[thread overview]
Message-ID: <4.2.0.58.19990826121935.00fc6c30@204.151.72.2> (raw)
In-Reply-To: <Pine.LNX.3.96.990826125142.20183A-100000@zeke.sympatico.ca >


>
>PROS
>- LVM is almost a necessity when managing large amounts of storage.

although at some cost in performance since there's an additional layer of
translation before you get to the actual disk blocks....

>- Many unix people think that storage layout is one of the most difficult
>aspects of maintaining a system. LVM simply makes storage management much
>more flexible by allowing storage to be reallocated easily at anytime.

at some cost again....insulation from actual details of storage does mean you
are not necessarily making the optimal use of layout....but the benefits seem
to far outweigh these costs.

>- Folks coming to Linux from other UNIXes which use an LVM (HP, AIX etc..)
>will be familiar and comfortable with LVM concepts and will more readily
>embrace the penguin.

add at least Solaris (Solstice Disk Suite) and SGI IRIX  (xlv - a very nice
combination with the xfs filesystem) to this list.

>- The "out of storage space" is a very common problem for users especially
>new users. LVM makes resizing allocated space easier. This is perhaps the
>most common problem I here about from new users.
>- LVM is not a new concept and has been proven to be indispensible in
>other OSes, (ie. It is not just some hair-brained scheme that just makes
>things harder to learn and more complicated).
>
>CONS
>- Using LVM is by definition adding a another logical layer for storage.
>Users not already familiar with an LVM will have to do some learning, or
>not use LVM.

Not terribly familiar with Linux LVM (listening here to help become so)...other
LVMs require a large number of commands to become familar with (the AIX
LVM being the prototype which _most_ folks have followed; Solaris takes
a somewhat different approach).  Actually, a well-thought out GUI can be
a great help here.  The author of a course I teach has constructed one as
a sample which gives you drag-and-drop LVM management - in very little
tk/perl code.

       reply	other threads:[~1999-08-26 18:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.3.96.990826125142.20183A-100000@zeke.sympatico.ca >
1999-08-26 18:30 ` Mats Wichmann [this message]
1999-08-26 19:28   ` [linux-lvm] LVM in stock kernel!? S. Ryan Quick
1999-08-26 17:33 Shane Shrybman
1999-08-26 20:26 ` Heinz Mauelshagen
  -- strict thread matches above, loose matches on Subject: below --
1999-08-23 16:37 [linux-lvm] LVM in stock kernel! Drew Smith
1999-08-23 14:25 [linux-lvm] LVM in stock kernel!? Adams, Mark
1999-08-21 20:39 Heinz Mauelshagen
1999-08-21 21:17 ` Marcus Ruehmann
1999-08-21 22:56   ` James Pattinson
1999-08-24 19:32     ` Shane Shrybman
1999-08-24 20:28       ` Jonny B.
1999-08-25  1:35         ` [linux-lvm] LVM in stock kernel! Shane Shrybman
1999-08-25 17:23         ` [linux-lvm] LVM in stock kernel!? Luca Berra
1999-08-24 23:20       ` Heinz Mauelshagen
1999-08-22 11:24   ` Ulrik De Bie
1999-08-22  6:16 ` pamvdam
1999-08-22 11:14   ` Heinz Mauelshagen
1999-08-22 15:07     ` pamvdam
1999-08-23  7:50       ` Heinz Mauelshagen
1999-08-23  7:11 ` Klaus Strebel
1999-08-23 17:41 ` Luca Berra
1999-08-23 19:15   ` Marcus Ruehmann

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=4.2.0.58.19990826121935.00fc6c30@204.151.72.2 \
    --to=mats@laplaza.org \
    --cc=linux-lvm@msede.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).