From: Mike Fedyk <mfedyk@matchmail.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: "Ramy M. Hassan" <ramy@gawab.com>, linux-kernel@vger.kernel.org
Subject: Re: Advanced storage management ( suggestion )
Date: Sat, 06 Mar 2004 22:08:52 -0800 [thread overview]
Message-ID: <404ABC74.7030607@matchmail.com> (raw)
In-Reply-To: <16458.42370.917655.953328@notabene.cse.unsw.edu.au>
Neil Brown wrote:
> On Saturday March 6, mfedyk@matchmail.com wrote:
>
>>>2- Support for multi-disk/multi-host storage pool.
>>
>>You're mixing layers here. MD and DM already work in this area.
>>
>
>
> I would probably disagree here.
> I think it makes much more sense for a filesystem to know about
> multiple devices than for MD or DM to combine a bunch of devices into
> the illusion of one big device, only to have the filesystem chop that
> big device into little files....
>
> (Note that I wouldn't expect a filesystem to include raid5 style
> behaviour, and probably wouldn't expect raid1 like behaviour, but
> having the filesystem do striping and inter-device migration itself
> seems eminently sensible.)
>
I saw something doing that in a SAN. Don't know if it was at the
filesytem level though.
> However I don't see much value if the suggestion of a new layer that
> provide lots of services of filesystems. I strongly suspect that no
> filesystem would want to use them. Look at "jdb". It is designed to
> provide a journalling layer for any filesystem, but how many
> filesystems use it? Just one - ext3 - the one it was designed for.
Since JBD is "Journaled Block Device", does that mean it's meant for
block based journaling instead of "virtual" (I don't think I'm using the
right term, so please someone correct me) journaling?
Mike
next prev parent reply other threads:[~2004-03-07 6:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 19:44 Advanced storage management ( suggestion ) Ramy M. Hassan
2004-03-07 3:34 ` Mike Fedyk
2004-03-07 4:30 ` Neil Brown
2004-03-07 6:08 ` Mike Fedyk [this message]
2004-03-09 16:38 ` Jeremy Jackson
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=404ABC74.7030607@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=ramy@gawab.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