public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: what is our answer to ZFS?
Date: 29 Nov 2005 06:58:55 -0700	[thread overview]
Message-ID: <p73zmnnh7xc.fsf@verdi.suse.de> (raw)
In-Reply-To: <20051129050439.GB22879@thunk.org>

Theodore Ts'o <tytso@mit.edu> writes:

> On Mon, Nov 28, 2005 at 01:53:51PM +0100, Lars Marowsky-Bree wrote:
> > On 2005-11-21T11:19:59, J?rn Engel <joern@wohnheim.fh-wedel.de> wrote:
> > 
> > > o Merge of LVM and filesystem layer
> > >   Not done.  This has some advantages, but also more complexity than
> > >   seperate LVM and filesystem layers.  Might be considers "not worth
> > >   it" for some years.
> > 
> > This is one of the cooler ideas IMHO. In effect, LVM is just a special
> > case filesystem - huge blocksizes, few files, mostly no directories,
> > exports block instead of character/streams "files".
> 
> This isn't actually a new idea, BTW.  Digital's advfs had storage
> pools and the ability to have a single advfs filesystem spam multiple
> filesystems, and to have multiple adv filesystems using storage pool,
> something like ten years ago.

The old JFS code base had something similar before it got ported
to Linux (I believe it came from OS/2). But it was removed.
And miguel did a prototype of it with ext2 at some point long ago.

But to me it's unclear it's a really good idea. Having at least the option
to control where physical storage is placed is nice, especially 
if you cannot mirror everything (ZFS seems to assume everything is mirrored)
And separate devices and LVM make that easier.

-Andi

  parent reply	other threads:[~2005-11-29  9:30 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21  9:28 what is our answer to ZFS? Alfred Brons
2005-11-21  9:44 ` Paulo Jorge Matos
2005-11-21  9:59   ` Alfred Brons
2005-11-21 10:08     ` Bernd Petrovitsch
2005-11-21 10:16     ` Andreas Happe
2005-11-21 11:30       ` Anton Altaparmakov
2005-11-21 10:19     ` Jörn Engel
2005-11-21 11:46       ` Matthias Andree
2005-11-21 12:07         ` Kasper Sandberg
2005-11-21 13:18           ` Matthias Andree
2005-11-21 14:18             ` Kasper Sandberg
2005-11-21 14:41               ` Matthias Andree
2005-11-21 15:08                 ` Kasper Sandberg
2005-11-22  8:52                   ` Matthias Andree
2005-11-21 22:41               ` Bill Davidsen
2005-11-21 20:48             ` jdow
2005-11-22 11:17               ` Jörn Engel
2005-11-21 11:59       ` Diego Calleja
2005-11-22  7:51       ` Christoph Hellwig
2005-11-22 10:28         ` Jörn Engel
2005-11-22 14:50         ` Theodore Ts'o
2005-11-22 15:25           ` Jan Harkes
2005-11-22 16:17             ` Chris Adams
2005-11-22 16:55               ` Anton Altaparmakov
2005-11-22 17:18                 ` Theodore Ts'o
2005-11-22 19:25                   ` Anton Altaparmakov
2005-11-22 19:52                     ` Theodore Ts'o
2005-11-22 20:00                       ` Anton Altaparmakov
2005-11-22 23:02                         ` Theodore Ts'o
2005-11-22 21:14                       ` Bill Davidsen
2005-11-22 21:06                 ` Bill Davidsen
2005-11-22 20:19               ` Alan Cox
2005-11-22 19:56                 ` Chris Adams
2005-11-22 21:19                   ` Bill Davidsen
2005-11-23 19:20                   ` Generation numbers in stat was Re: what is slashdot's " Andi Kleen
2005-11-24  5:15                     ` Chris Adams
2005-11-24  8:47                       ` Andi Kleen
2005-11-22 16:28             ` what is our " Theodore Ts'o
2005-11-22 17:37               ` Jan Harkes
2005-11-22 16:36                 ` Jeff V. Merkey
2005-11-28 12:53       ` Lars Marowsky-Bree
2005-11-29  5:04         ` Theodore Ts'o
2005-11-29  5:57           ` Willy Tarreau
2005-11-29 14:42             ` John Stoffel
2005-11-29 13:58           ` Andi Kleen [this message]
2005-11-29 16:03           ` Chris Adams
2005-11-21 11:45     ` Diego Calleja
2005-11-21 14:19       ` Tarkan Erimer
2005-11-21 18:52         ` Rob Landley
2005-11-21 19:28           ` Diego Calleja
2005-11-21 20:02           ` Bernd Petrovitsch
2005-11-22  5:42             ` Rob Landley
2005-11-22  9:25               ` Matthias Andree
2005-11-21 23:05           ` Bill Davidsen
2005-11-22  0:15           ` Bernd Eckenfels
2005-11-21 22:59             ` Jeff V. Merkey
2005-11-22  7:45               ` Christoph Hellwig
2005-11-22  9:19                 ` Jeff V. Merkey
2005-11-22 16:00               ` Bill Davidsen
2005-11-22 16:09                 ` Jeff V. Merkey
2005-11-22 20:16                   ` Bill Davidsen
2005-11-22 16:14                 ` Randy.Dunlap
2005-11-22 16:38                   ` Steve Flynn
2005-11-22  7:15             ` Rob Landley
2005-11-22  8:16               ` Bernd Eckenfels
2005-11-22  0:45           ` Pavel Machek
2005-11-22  6:34             ` Rob Landley
2005-11-22 19:05               ` Pavel Machek
2005-11-22  9:20           ` Matthias Andree
2005-11-22 10:00             ` Tarkan Erimer
2005-11-22 15:46               ` Jan Dittmer
2005-11-22 16:27               ` Bill Davidsen
2005-11-21 18:17       ` Rob Landley
  -- strict thread matches above, loose matches on Subject: below --
2005-11-24  1:52 art

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=p73zmnnh7xc.fsf@verdi.suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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