From: Theodore Tso <tytso@mit.edu>
To: Eric Anopolsky <erpo41@gmail.com>
Cc: postrishi <postrishi@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: Porting Zfs features to ext2/3
Date: Mon, 28 Jul 2008 08:40:55 -0400 [thread overview]
Message-ID: <20080728124055.GD9378@mit.edu> (raw)
In-Reply-To: <1217218559.28825.12.camel@telesto>
On Sun, Jul 27, 2008 at 10:15:59PM -0600, Eric Anopolsky wrote:
> It's true that ZFS on FUSE performance isn't all it could be right now.
> However, ZFS on FUSE is currently not taking advantage of mechanisms
> FUSE provides to improve performance. For an example of what can be
> achieved, check out http://www.ntfs-3g.org/performance.html .
Yes... and take a look at the metadata operations numbers. FUSE can
do things to accellerate bulk read/write, but metadata-intensive
operations will (I suspect) always be slow. I also question whether
the FUSE implementation will have the safety that has always been the
Raison d'être of ZFS. Have you or the ZFS/FUSE developers done tests
where you are writing to the filesystem, and then someone pulls the
plug on the fileserver while ZFS is writing? Does the filesystem
recovery cleanly from such a scenario?
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-07-28 12:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 8:49 Porting Zfs features to ext2/3 postrishi
2008-07-27 22:49 ` Theodore Tso
2008-07-27 22:49 ` Shehjar Tikoo
2008-07-27 23:37 ` Theodore Tso
2008-07-28 3:42 ` Shehjar Tikoo
2008-07-27 22:54 ` Eric Anopolsky
2008-07-27 23:38 ` Theodore Tso
2008-07-28 4:15 ` Eric Anopolsky
2008-07-28 12:40 ` Theodore Tso [this message]
2008-07-29 3:58 ` Eric Anopolsky
2008-07-29 16:46 ` Ric Wheeler
2008-07-30 6:00 ` Eric Anopolsky
2008-07-29 21:00 ` Szabolcs Szakacsits
2008-07-29 22:52 ` Szabolcs Szakacsits
2008-07-30 1:29 ` Theodore Tso
2008-08-07 12:09 ` Goswin von Brederlow
2008-07-30 1:34 ` Theodore Tso
2008-07-31 0:50 ` Szabolcs Szakacsits
2008-08-04 20:38 ` Szabolcs Szakacsits
2008-08-07 12:01 ` Goswin von Brederlow
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=20080728124055.GD9378@mit.edu \
--to=tytso@mit.edu \
--cc=erpo41@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=postrishi@gmail.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;
as well as URLs for NNTP newsgroup(s).