From: Hans Reiser <reiser@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, reiserfs-dev@namesys.com
Subject: Re: kmail slowdown on 2.6.* +reiserFS (v3)
Date: Wed, 14 Jan 2004 16:32:08 +0300 [thread overview]
Message-ID: <400544D8.5090005@namesys.com> (raw)
In-Reply-To: <1074086445.32706.1013.camel@tiny.suse.com>
Chris Mason wrote:
>On Sun, 2004-01-11 at 21:27, Andrew Morton wrote:
>
>
>>Ciaby <ciaby@autistici.org> wrote:
>>
>>
>>>I all!
>>>I've recently upgraded from 2.4 to 2.6 and I've noticed a strange thing:
>>>on the 2.4 kernel, kmail run decently (i've an old k6-200).
>>>On the 2.6 kernel, kmail slowdown and take a very long time to read a mailbox.
>>>I think something changed in the reiserFS during this time...
>>>I'm not the only experiencing this problem, read this:
>>>http://kerneltrap.org/node/view/1844
>>>
>>>
>>A buglet in kmail was tripped up by some optimisations which went into
>>reiserfs.
>>
>>Upgrading kmail should fix it up. Or mount the reiserfs filesystems with
>>the `nolargeio=1' mount option.
>>
>>
>
>Actually, we've hit other problems with v3 largeio, it can confuse rpm
>badly. The real bug is apparently in bdb, the larger io size suggested
>by the filesystem lead bdb to corrupt its own files. I spent some time
>neck deep in the db code but couldn't track the problem down.
>
>I seem to remember the XFS folks hitting exactly the same bug.
>
>Hans, can I talk you into having v3 export an io size of 4k to userspace
>again? Applications that send large ios would still use Oleg's
>optimized file write paths.
>
>-chris
>
>
>
>
>
>
why is it you don't want to "fix" bdb to lie to itself about the result
of statfs?
--
Hans
next prev parent reply other threads:[~2004-01-14 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-11 20:09 kmail slowdown on 2.6.* +reiserFS (v3) Ciaby
2004-01-12 2:27 ` Andrew Morton
2004-01-14 13:20 ` Chris Mason
2004-01-14 13:32 ` Hans Reiser [this message]
2004-01-14 13:42 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2004-01-12 13:18 Samium Gromoff
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=400544D8.5090005@namesys.com \
--to=reiser@namesys.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=reiserfs-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox