From: mjt@nysv.org
To: Alex Zarochentsev <zam@namesys.com>
Cc: Will Smith <will@willsmith.org>, reiserfs-list@namesys.com
Subject: Re: Benchmark : ext3 vs reiser4 and effects of fragmentation.
Date: Thu, 16 Sep 2004 16:08:09 +0300 [thread overview]
Message-ID: <20040916130809.GI26192@nysv.org> (raw)
In-Reply-To: <20040916085248.GI5137@backtop.namesys.com>
On Thu, Sep 16, 2004 at 12:52:49PM +0400, Alex Zarochentsev wrote:
>> 3) the repacker can bring performance of reiser4 back
>> to full speed, but only if run several times.
>yes, we had similar results. it is so cool that reiser4 repacker effect
>is visible outside namesys :)
S'cuse me, but why does it have to be run several times?
A bug to be fixed?
>> 4) the repacker is not yet stable - I had to run fsck
>> a few times after repacking, and once got a kernel
>> stack trace during repacking resulting in an
>> un-unmountable filesystem.
>unmergable units shouldn't be problem for the reiser4 kernel code.
What are their significance; what do they mean?
Basically warnings are scary, even if they were harmless :)
Thanks!
--
mjt
next prev parent reply other threads:[~2004-09-16 13:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 22:02 Benchmark : ext3 vs reiser4 and effects of fragmentation Will Smith
2004-09-16 8:52 ` Alex Zarochentsev
2004-09-16 13:08 ` mjt [this message]
2004-09-16 14:50 ` Will Smith
2004-09-16 15:03 ` mjt
2004-09-16 17:16 ` Hans Reiser
2004-09-16 15:38 ` Alex Zarochentsev
2004-09-16 15:52 ` mjt
2004-09-16 17:26 ` Hans Reiser
2004-09-16 18:38 ` Alex Zarochentsev
2004-09-16 19:00 ` mjt
2004-09-16 19:05 ` Chris Mason
2004-09-17 2:29 ` Hans Reiser
2004-09-17 17:01 ` Philippe Gramoullé
2004-09-16 15:38 ` Christian Mayrhuber
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=20040916130809.GI26192@nysv.org \
--to=mjt@nysv.org \
--cc=reiserfs-list@namesys.com \
--cc=will@willsmith.org \
--cc=zam@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.