I had a look at the appropriate mailing list http://marc.theaimsgroup.com/?l=reiserfs&m=106311926125192&w=2 and think this patch ftp://ftp.suse.com/pub/people/mason/patches/data-logging/2.4.21/03-relocation-8.diff.gz is really missing. Read also http://forums.gentoo.org/viewtopic.php?p=750238 for more information about the problems. Reproducible: Always Steps to Reproduce: 1. 2. 3.
That post from Oleg says that it's fixed in 2.4.22. Are you using gentoo-sources-2.4.22-r2?
No, I use the latest stable 2.4.20. Fetched gentoo-sources-2.4.22, but couldn't find it in patches.txt...
@Brian: Thanks for letting this report open. I just got the rtc fixe via emerge sync and test if the problem persists or if the changes in vanilla sources solve the problem. Two issues: 1. I can't understand that the stable(!) gentoo-sources-2.4.22 didn't got a revision update. It's a security fix!! 2. You'll have a close look at kernel mailing-lists and so on, but a lot of users won't. I for one have to say, I should have had a look before posting this bug report, but in general I have to say: These are the official Gentoo sources. There should be something like a short summary what changed, as a hint when to upgrade. Also the urls of kernel changelogs should be part of the gentoo changelog - or maybe downloaded with the kernels.
Carlo: I've just bumped the security upgrade and a GLSA will be released within 48 hours, by when all the kernels in the tree should be patched.
plasmaroo: O.k. - just wondered to see getting .20 a new revision, but .22 not. Sailing round all known bugs, the kernel compiled fine and the reiserfs problem is fixed. If no one cares about my 2nd issue, this bug can be closed. btw.: This thread http://forums.gentoo.org/viewtopic.php?t=119590 discusses a possible problem with the kernel. I couldn't find a related bug report.
Closing as asked. 2.4.20-r10 and 2.4.22-r3 are the new revisions and should be in CVS from a couple of hours ago. Kernel changes should be listed in the ChangeLog, BTW.
*** Bug 42097 has been marked as a duplicate of this bug. ***