Bug 680127

Summary: cachefilesd creates lot of 'Scan complete' messages in /var/log/messages
Product: [Fedora] Fedora Reporter: JM <igeorgex>
Component: cachefilesdAssignee: David Howells <dhowells>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 14CC: dhowells, mikey, steved
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 13:05:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description JM 2011-02-24 12:52:09 UTC
The 'cachefilesd' creates lot of 'Scan complete' messages in /var/log/messages when '/var/cache/fscache/cache' is empty. That's important the Cache directory must be empty, the moment it fills up with cache files, the message is gone.

With an empty cache directory the daemon creates every minute 2 messages in /var/log/messages and fills up the logfile.

Feb 24 13:29:02 foobar cachefilesd[8019]: Scan complete
Feb 24 13:29:32 foobar cachefilesd[8019]: Scan complete

The problem is line 1325 in cachefilesd.c

----------
    scan = curr->parent;
    if (!scan) {
        info("Scan complete");
        decant_cull_table();
    }

    debug(2, "<-- build_cull_table({%s})", curr->name);
    put_object(curr);
    return;
----------

Maybe a solution would be to replace 'info("Scan complete")' with 'debug(2, "Scan complete")'? This way you still get the message if you raise the debug level but under normal conditions the daemon would be silent and does not fill /var/log/messages with 'Scan complete' messages.

Version of cachefilesd is:

cachefilesd-0.10.1-2.fc14

Comment 1 G. Michael Carter 2011-10-25 16:22:00 UTC
Any news on this one?  I'm in the same situation with 0.10.1-3.fc15

Comment 2 G. Michael Carter 2011-10-25 16:22:47 UTC
Oh and I should include, I'm getting it way more frequent.

Oct 25 11:41:34 whitestar cachefilesd[1615]: Scan complete
Oct 25 11:41:34 whitestar cachefilesd[1615]: Scan complete
Oct 25 11:41:34 whitestar cachefilesd[1615]: Scan complete
Oct 25 11:41:34 whitestar cachefilesd[1615]: Scan complete
Oct 25 11:41:34 whitestar cachefilesd[1615]: Scan complete
Oct 25 11:41:34 whitestar cachefilesd[1615]: Scan complete
Oct 25 11:41:34 whitestar cachefilesd[1615]: Scan complete

Comment 3 Fedora End Of Life 2012-08-16 13:05:51 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. 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 '14' 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 14 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