public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: David Weinehall <tao@acc.umu.se>
Cc: Austin Gonyou <austin@digitalroadkill.net>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Mark Peloquin <peloquin@us.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [2.6] Most likely to be merged by Halloween... THE LIST
Date: Sat, 20 Jul 2002 15:24:14 -0600	[thread overview]
Message-ID: <20020720212414.GL10315@clusterfs.com> (raw)
In-Reply-To: <20020720205520.GX29001@khan.acc.umu.se>

On Jul 20, 2002  22:55 +0200, David Weinehall wrote:
> On Sat, Jul 20, 2002 at 03:30:29PM -0500, Austin Gonyou wrote:
> > On Sat, 2002-07-20 at 16:05, Alan Cox wrote:
> > Just IMHO, LVM2 makes better sense as there currently is no "stable"
> > module for XFS in EVMS, AFAIK.
> > Also, LVM is currently in 2.4 and a lot of peopel use it, LVM2 seems to
> > be the proper progression for 2.6. My $0.02
> 
> I'd rather see the EVMS go in, if a choice has to be made between the
> two. EVMS seems to have a lot of effort put in it, and has the
> experience from the (very good) volume-managers that IBM have in OS/2
> and AIX.

I, for one, would like to have the choice to use the AIX LVM format, and
I'm sure that people thinking of migrating from HP/UX or whatever would
want to be able to add support for their on-disk LVM format.  It really
provides a framework to consolidate all of the partition/MD code into
a single place (e.g. RAID, LVM, LDM (windows NT), DOS, BSD, Sun, etc).

EVMS also allows things like creating snapshots and resizing for
partitions that were not originally set up as LVM volumes (i.e. you can
"upgrade" your existing DOS partitions in-place to support LVM features
instead of requiring a backup/restore cycle.

> Afaik, EVMS supports LVM volumes. As for XFS, I'm sure an XFS module can
> be produced for EVMS (then again, XFS isn't merged yet either...)

Even if there is no XFS FSIM module for EVMS, it doesn't mean you can't
use XFS filesystems on EVMS volumes.  The only thing it means is that you
don't get integrated volume+filesystem resize+don't shoot foot support.

Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/


  reply	other threads:[~2002-07-20 21:24 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-19 14:05 [2.6] Most likely to be merged by Halloween... THE LIST Mark Peloquin
2002-07-20 21:05 ` Alan Cox
2002-07-20 20:30   ` Austin Gonyou
2002-07-20 20:55     ` David Weinehall
2002-07-20 21:24       ` Andreas Dilger [this message]
2002-07-21  0:24         ` Alan Cox
2002-07-21  1:47           ` Andreas Dilger
2002-07-26  8:52             ` Heinz J . Mauelshagen
2002-07-21 20:44       ` Ernst Lehmann
  -- strict thread matches above, loose matches on Subject: below --
2002-07-26 16:12 Ben Rafanello
2002-07-29  9:00 ` Joe Thornber
2002-07-25 17:36 Ben Rafanello
2002-07-26  8:16 ` Joe Thornber
2002-07-22 23:47 Ben Rafanello
2002-07-22 21:42 Steve Pratt
2002-07-23  8:16 ` Joe Thornber
2002-07-22 18:31 Ben Rafanello
2002-07-22 19:07 ` Christoph Hellwig
2002-07-23  8:26 ` Joe Thornber
     [not found] <OF918E6F71.637B1CBC-ON85256BFB.004CDDD0@pok.ibm.com.suse.lists.linux.kernel>
     [not found] ` <1027199147.16819.39.camel@irongate.swansea.linux.org.uk.suse.lists.linux.kernel>
2002-07-21  6:57   ` Andi Kleen
2002-07-21  7:23     ` Austin Gonyou
2002-07-21  8:33     ` Oliver Neukum
2002-07-21  8:47       ` Andi Kleen
2002-07-21 13:40     ` Alan Cox
2002-07-21 14:10       ` Andi Kleen
2002-07-21 15:52         ` Alasdair Kergon
2002-07-23 16:41       ` Timothy D. Witham
2002-07-21  4:42 Tom Walcott
2002-07-21 13:48 ` Alan Cox
2002-07-21 16:39   ` Tom Walcott
2002-07-19  2:00 Val Henson
2002-07-18 11:57 Martin Knoblauch
2002-07-18  4:49 Guillaume Boissiere
2002-07-18  6:08 ` Greg KH
2002-07-18 16:14   ` Greg KH
2002-07-20  7:41     ` Shane Nay
2002-07-20  8:22       ` Russell King
     [not found]     ` <200207200805.BAA20399@granite.he.net>
2002-07-20 17:27       ` Greg KH
2002-07-18  8:20 ` Dave Jones
2002-07-18  8:36 ` Stephen Lord
2002-07-18  9:23 ` Tomas Szepe
2002-07-18 14:31 ` Martin J. Bligh
2002-07-18 16:47   ` Anton Blanchard
2002-07-19 15:08   ` Hubertus Franke
2002-07-18 16:15 ` Greg KH
2002-07-18 16:17 ` Greg KH
2002-07-18 16:39 ` Robert Love
2002-07-18 22:19   ` Rik van Riel
2002-07-18 16:46 ` Bill Davidsen
2002-07-18 20:22   ` Dave Jones
2002-07-18 23:17     ` Thunder from the hill
2002-07-19  1:18     ` Peter Osterlund
2002-07-19  9:40       ` Peter Osterlund
2002-07-23  9:39         ` Jens Axboe
2002-07-23 13:09           ` Peter Osterlund
2002-07-24  6:24             ` Jens Axboe
2002-07-20 13:06     ` Miles Lane
2002-07-22 20:50     ` Bill Davidsen
2002-07-19  4:45   ` Guillaume Boissiere
2002-07-19 17:31 ` William Lee Irwin III
2002-07-22 10:23 ` Joe Thornber
2002-07-22 15:22   ` Daniel Phillips
2002-07-22 16:57     ` Alan Cox
2002-07-22 16:45       ` Daniel Phillips
2002-07-22 18:00         ` Alan Cox
2002-07-23 22:33     ` Bill Davidsen
     [not found] <OF918E6F71.637B1CBC-ON85256BFB.004CDDD0@pok.ibm.com.suse.lists.linux.kernel >

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=20020720212414.GL10315@clusterfs.com \
    --to=adilger@clusterfs.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=austin@digitalroadkill.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peloquin@us.ibm.com \
    --cc=tao@acc.umu.se \
    /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