Summary: | net-fs/openafs-1.4.7 kernel Oops on 2.6.25-r4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael Hammer (RETIRED) <mueli> |
Component: | New packages | Assignee: | Stefaan De Roeck (RETIRED) <stefaan> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | hrabe |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 218127 |
Description
Michael Hammer (RETIRED)
2008-05-23 14:39:12 UTC
Thanks for the thorough analysis. If I get this correctly, the choice is between * a system that runs out of PAGs, which amounts to a DOS on heavily used systems * a system that may crash because of some lock error in the garbage collection (correct me if I'm wrong) so the safe choice on a 2.6.25 kernel seems to be disabling gcpags, which I would consider to change in the source, as this default is a configuration parameter. I have not yet seen the crash you're describing, but then again my machine does not undergo heavy afs traffic at the moment. I'm checking with #220635 anyway to see whether they're affected by the same bug (locking errors may have varying consequences). Hoping for more information on the OpenAFS mailing lists... I forgot to mention that on my system (2.6.25-gentoo-r1 with openafs-1.4.7), /proc/sys/afs/GCPAGs jumps from 1 (enabled) to 8 (error condition) after some time. I do fully agree that both possibilities aren't nice. I do _not_ demand that you undef GCPAGs per default - that make no sense. I am going to make a patch on my affected machines. Let's hope that upstream will fix the issue - I am willing to do further testing if I can help in any way.... it seams you're watching the bug - don't hesitate to ping me ;) @/proc/sys/afs/GCPAGs : I can attest that at the momemt of the kernel Oops /proc/sys/afs/GCPAGs hasn't reached an error state. Perhaps this is the difference between your running and my segfaulting machines? So far and thx for all the fish mueli BTW: Sry Stefaan for misspelling your name! Upstream still doesn't seem to have a release that solves this problem. I'm beginning to think we'll need to pull patches from cvs (again). *** Bug 232588 has been marked as a duplicate of this bug. *** Could you check whether this works for you in net-fs/openafs-1.4.8? Thanks The problem is under control for me. With openafs-1.4.8 I wasn't able to reproduce the problem yet. On the other hand it's fully an upstream issue and therefore I'll close this bug. g, mueli |