+++ This bug was initially created as a clone of Bug #716803 +++ Created attachment 510027 [details] Screen dump of a crash Description of problem: Kernel crashes reliably with "CacheFiles: Error: Object already preemptively buried" error when runnign under higher load Version-Release number of selected component (if applicable): kernel-2.6.38.8-32.fc15.x86_64 cachefilesd-0.10.1-3.fc15.x86_64 How reproducible: Reliably. Steps to Reproduce: 1. Mount file system from NFS server using NFS4 with fsc option like that: castor-vlab:/home/ on /home type nfs4 (rw,noatime,vers=4,rsize=8192,wsize=8192,namlen=255,soft,proto=tcp,port=0,timeo=14,retrans=2,sec=sys,clientaddr=192.168.1.1,minorversion=0,fsc,local_lock=none,addr=192.168.1.2) 2. Make sure cachefilesd is configured and running 3. run several tasks that case high NFS traffic, especially accessing the same set of files from multiple jobs (like building the same software package in parallel) Actual results: Kernel crashes in fscache / cachefiles routines Expected results: no crash Additional info: --- Additional comment from endoflife on 2012-08-07 12:08:13 EDT --- This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.