kmail slowdown on 2.6.* +reiserFS (v3)
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
Please CC me if there's some reply.
tnx all for the good work! :-)
Bye
Signature · 6 lines
-----> \|/Ciaby\|/ <------ ! E-mail:[email protected] ! ! ICQ:59493039 ! ! SpinHacker404 HackLab ! ! www.ecn.org/sh404 ! gpg --keyserver autistici.org --recv-key 42F3C487
Quoted 8 lines · Ciaby
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.
Quoted 10 lines · Andrew Morton
Quoted 8 lines · Ciaby
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
Quoted 5 lines
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
Quoted 28 lines · Chris Mason
Quoted 12 lines · Andrew Morton
Quoted 9 lines · Ciaby
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/1844Quoted 7 lines
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.
Quoted 13 lines
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?
Signature · 1 line
Hans
Quoted 30 lines · Hans Reiser
Quoted 28 lines · Chris Mason
Quoted 12 lines · Andrew Morton
Quoted 9 lines · Ciaby
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/1844Quoted 7 lines
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.
Quoted 8 lines
Quoted 6 lines
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.
why is it you don't want to "fix" bdb to lie to itself about the result of statfs?
Because I'm worried that bdb isn't the only app having problems ;-) And it's important enough as a legacy app that I don't want to tell everyone they must upgrade to some hacked bdb version in order for v3 to work under 2.6.x
-chris