From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: linux-raid@vger.kernel.org
Subject: suns raid-z / zfs
Date: Sun, 17 Feb 2008 17:04:03 +0100 [thread overview]
Message-ID: <20080217160403.GA15710@rap.rap.dk> (raw)
Hi
any opinions on suns zfs/raid-z?
It seems like a good way to avoid the performance problems of raid-5
/raid-6
But does it stripe? One could think that rewriting stripes
other places would damage the striping effects.
Or is the performance only meant to be good for random read/write?
Can the code be lifted to Linux? I understand that it is already in
freebsd. Does Suns licence prevent this?
And could something like this be built into existing file systems like
ext3 and xfs? They could have a multipartition layer in their code, and
then the heuristics to optimize block access could also apply to stripe
access.
best regards
keld
next reply other threads:[~2008-02-17 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 16:04 Keld Jørn Simonsen [this message]
2008-02-18 4:07 ` suns raid-z / zfs Neil Brown
2008-02-18 5:33 ` Keld Jørn Simonsen
2008-02-18 10:51 ` Neil Brown
2008-02-18 20:45 ` Keld Jørn Simonsen
2008-02-21 10:37 ` Mario 'BitKoenig' Holbe
2008-02-26 20:27 ` Bill Davidsen
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=20080217160403.GA15710@rap.rap.dk \
--to=keld@dkuug.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).