From: Neil Brown <neilb@suse.de>
To: "Keld Jørn Simonsen" <keld@dkuug.dk>
Cc: Neil Brown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: suns raid-z / zfs
Date: Mon, 18 Feb 2008 21:51:15 +1100 [thread overview]
Message-ID: <18361.25379.998485.63488@notabene.brown> (raw)
In-Reply-To: message from Keld Jorn Simonsen on Monday February 18
On Monday February 18, keld@dkuug.dk wrote:
> On Mon, Feb 18, 2008 at 03:07:44PM +1100, Neil Brown wrote:
> > On Sunday February 17, keld@dkuug.dk wrote:
> > > Hi
> > >
> >
> > > It seems like a good way to avoid the performance problems of raid-5
> > > /raid-6
> >
> > I think there are better ways.
>
> Interesting! What do you have in mind?
A "Log Structured Filesystem" always does large contiguous writes.
Aligning these to the raid5 stripes wouldn't be too hard and then you
would never have to do any pre-reading.
>
> and what are the problems with zfs?
Recovery after a failed drive would not be an easy operation, and I
cannot imagine it being even close to the raw speed of the device.
>
> > >
> > > But does it stripe? One could think that rewriting stripes
> > > other places would damage the striping effects.
> >
> > I'm not sure what you mean exactly. But I suspect your concerns here
> > are unjustified.
>
> More precisely. I understand that zfs always write the data anew.
> That would mean at other blocks on the partitions, for the logical blocks
> of the file in question. So the blocks on the partitions will not be
> adjacant. And striping will not be possible, generally.
The important part of striping is that a write is spread out over
multiple devices, isn't it.
If ZFS can choose where to put each block that it writes, it can
easily choose to write a series of blocks to a collection of different
devices, thus getting the major benefit of striping.
NeilBrown
next prev parent reply other threads:[~2008-02-18 10:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 16:04 suns raid-z / zfs Keld Jørn Simonsen
2008-02-18 4:07 ` Neil Brown
2008-02-18 5:33 ` Keld Jørn Simonsen
2008-02-18 10:51 ` Neil Brown [this message]
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=18361.25379.998485.63488@notabene.brown \
--to=neilb@suse.de \
--cc=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).