From: hpuxadm@choice.net
To: Dale Kemp <dale@inet.net.nz>
Cc: Linux LVM mailing list <linux-lvm@msede.com>
Subject: Re: [linux-lvm] Re: IBM to release LVM Technology to the Linux
Date: Fri, 23 Jun 2000 07:52:00 -0500 [thread overview]
Message-ID: <200006231252.HAA26966@mailgw00.execpc.com> (raw)
After seeing a few comments left by various users on this subject, I
would like to throw in my two cents that from an "admin" perspective,
this type of effort from a major vendor can only be a good thing.
However, just like anyone else who has watched the "major"
vendors(Compaq, HP, IBM) embrace Microsoft in the early 1990's, I
begin to wonder what the goal is with this project. Is IBM's
implementation of LVM going to remain free(gasp!), or is the goal to
start beta testing on Linux now only to offer LVM at a premium price
later? LVM solutions that are offered by IBM, SUN, and HP are all
excellent! However, you pay for them big time when you start getting
into advanced volume management issues. I have looked over the
datasheet that your website provides and am impressed with what you
are doing technically. What I am curious about is what will happen
once your implementation evolves to a "production ready" status. I
guess what I am more or less asking is, am I wasting my time following
IBM's implementation of LVM due to the fact that once it does leave
the development stage I will end up paying thousands of dollars per
seat for it?
Thoughts?
- Christopher Briggs
consult@unixadministrator.com
> > Another thing to remember is that users want power without risk.
This is
> > especially true in the corporate world. To make it there, Linux
needs a
> > very powerful, flexible logical volume management system which
minimizes
> > the risk of losing data. This calls for an architecture which
integrates
> > all aspects of volume/disk management into a single, easy to use
entity.
> > All processes which could be automated should be automated to
prevent
> > "accidents", such as the improper shrinking of a volume containing
data.
> > Right now it is rather easy to accidentally shrink a volume before
> > shrinking the filesystem on the volume, or to shrink the
filesystem on the
> > volume by the wrong amount. Is fdisk volume group aware (have not
tried
> > this yet)? If it isn't, a user could make a mistake and delete a
partition
> > which belongs to a volume group. The current system has holes in
it, and
> > these holes need to be plugged before Linux can be a major player
in the
> > corporate world. These holes can be plugged in a patch work
fashion, or
> > they can be eliminated by adopting an architecture (not
necessarily the one
> > in the white paper) in which they don't exist or can't occur.
>
> % man e2fsadm
>
> DESCRIPTION
> e2fsadm allows resizing of a logical volume (see lvm(8),
> lvcreate(8)) containing an unmounted ext2 filesystem and
> then extending the filesystem by resize2fs(8) afterwards
> or reducing the filesystem first and then reducing the
> logical volume afterwards.
>
> First thing is Linux-LVM is still evolving and will only get better.
Now IBM
> and SGI have their own volume management systems which is fine, and
> porting them to Linux can only be a good thing too. At the end of
the day
> its the users in the community that choose. Now its in the community
and
> IBM users interest for IBM to port AIX systems to Linux, so people
can simply
> install Linux and use there existing AIX hard drives. The same goes
for SGI.
> And work is already underway with JFS and XFS for example.
> I actually like the system being evolved by Linux-LVM since it
follows the
> Unix
> philosophy do one thing and to it well (the opposite of Micr$oft).
>
> -- Dale.
>
>
next reply other threads:[~2000-06-23 12:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-23 12:52 hpuxadm [this message]
2000-06-23 15:20 ` [linux-lvm] Re: IBM to release LVM Technology to the Linux Jens Benecke
-- strict thread matches above, loose matches on Subject: below --
2000-06-30 20:50 benr
2000-06-30 20:28 benr
2000-06-30 20:53 ` Ragnar Kjørstad
2000-06-30 19:27 benr
2000-06-30 21:30 ` Dale Kemp
2000-06-30 23:05 ` Jens Benecke
2000-06-29 23:39 benr
2000-06-30 4:09 ` Dale Kemp
2000-06-30 9:34 ` Jan Niehusmann
2000-06-30 15:28 ` Ragnar Kjørstad
2000-06-29 5:32 Jean-Eric Cuendet
2000-06-29 10:49 ` Andi Kleen
2000-06-29 1:23 benr
2000-06-29 14:37 ` Ragnar Kjørstad
2000-06-26 21:44 benr
2000-06-27 3:53 ` Paul Jakma
2000-06-26 20:59 benr
2000-06-26 14:27 Wilson, Eric
2000-06-26 23:18 ` Dale Kemp
2000-06-27 2:02 ` Andi Kleen
2000-06-27 2:22 ` Dale Kemp
2000-06-27 2:13 ` Andreas Dilger
2000-06-23 21:04 benr
2000-06-23 23:49 ` Paul Jakma
2000-06-24 6:37 ` Dale Kemp
2000-06-24 18:07 ` S. Ryan Quick
2000-06-25 1:25 ` Dale Kemp
2000-06-26 6:31 ` Martin K. Petersen
2000-06-22 19:37 benr
2000-06-23 1:23 ` Dale Kemp
2000-06-23 20:55 ` Martin K. Petersen
2000-06-21 22:27 benr
[not found] <85256900.007B81E0.00@d54mta02.raleigh.ibm.com>
2000-06-18 22:51 ` Andreas Dilger
2000-06-21 17:28 ` Martin K. Petersen
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=200006231252.HAA26966@mailgw00.execpc.com \
--to=hpuxadm@choice.net \
--cc=dale@inet.net.nz \
--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 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.