From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
xfs@oss.sgi.com, linux-raid@vger.kernel.org
Subject: Re: bonnie++ benchmarks for ext2,ext3,ext4,jfs,reiserfs,xfs,zfs on software raid 5
Date: Mon, 30 Jul 2007 15:11:06 -0500 [thread overview]
Message-ID: <1185826266.9448.5.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707301021090.12456@p34.internal.lan>
On Mon, 2007-07-30 at 10:29 -0400, Justin Piszcz wrote:
> Overall JFS seems the fastest but reviewing the mailing list for JFS it
> seems like there a lot of problems, especially when people who use JFS > 1
> year, their speed goes to 5 MiB/s over time and the defragfs tool has been
> removed(?) from the source/Makefile and on Google it says not to use it
> due to corruption.
The defragfs tool was an unported holdover from OS/2, which is why it
was removed. There never was a working Linux version. I have some
ideas to improve jfs allocation to avoid fragmentation problems, but jfs
isn't my full-time job anymore, so I can't promise anything. I'm not
sure about the corruption claims. I'd like to hear some specifics on
that.
Anyway, for enterprise use, I couldn't recommend jfs, since there is no
full-time maintainer.
Thanks,
Shaggy
--
David Kleikamp
IBM Linux Technology Center
prev parent reply other threads:[~2007-07-30 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 14:29 bonnie++ benchmarks for ext2,ext3,ext4,jfs,reiserfs,xfs,zfs on software raid 5 Justin Piszcz
2007-07-30 19:07 ` Al Boldi
2007-07-30 19:39 ` Miklos Szeredi
2007-07-30 21:12 ` Justin Piszcz
2007-07-31 2:41 ` Theodore Tso
2007-07-30 20:11 ` Dave Kleikamp [this message]
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=1185826266.9448.5.camel@kleikamp.austin.ibm.com \
--to=shaggy@linux.vnet.ibm.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=xfs@oss.sgi.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).