On Sun, 2004-01-11 at 21:27, Andrew Morton wrote:why is it you don't want to "fix" bdb to lie to itself about the result of statfs?
Ciaby <ciaby@xxxxxxxxxxxxx> wrote:
I all!A buglet in kmail was tripped up by some optimisations which went into
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
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