From: Jacob Madsen <jacob@mungo.dk>
To: linux-raid@vger.kernel.org
Subject: Re: blog entry on RAID limitation
Date: Tue, 17 Jan 2006 17:42:02 +0100 [thread overview]
Message-ID: <43CD1E5A.3050802@mungo.dk> (raw)
In-Reply-To: <17356.51593.481883.173707@cse.unsw.edu.au>
Neil Brown wrote:
> In general, I think increasing the connection between the filesystem
> and the volume manager/virtual storage is a good idea. Finding the
> right balance is not going to be trivial. ZFS has taken one very
> interesting approach. There are others.
>
Just out of curiosity... When you say there are others, are you then
refering to existing solutions or just saying other approaches will be
developed in the future?
next prev parent reply other threads:[~2006-01-17 16:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8E5ACAE05E6B9E44A2903C693A5D4E8A097F6C86@hqemmail02.nvidia.com>
2006-01-17 8:45 ` blog entry on RAID limitation Jeff Breidenbach
2006-01-17 10:40 ` Neil Brown
2006-01-17 16:42 ` Jacob Madsen [this message]
2006-01-17 22:47 ` Neil Brown
2006-01-21 20:50 ` Carlos Carvalho
2006-01-24 3:20 ` Neil Brown
2006-01-21 20:43 ` Carlos Carvalho
2006-01-22 11:52 Rik Herrin
2006-01-22 23:08 ` Neil Brown
2006-01-27 13:09 ` Molle Bestefich
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=43CD1E5A.3050802@mungo.dk \
--to=jacob@mungo.dk \
--cc=linux-raid@vger.kernel.org \
/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).