Bug 1011119

Summary: Very long startup with cachefilesd
Product: Red Hat Enterprise Linux 6 Reporter: jcpunk
Component: cachefilesdAssignee: David Howells <dhowells>
Status: CLOSED WONTFIX QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: csieh, misterbonnie, riehecky
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-06 10:17:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description jcpunk 2013-09-23 16:10:35 UTC
Description of problem:
With cachefilesd enabled my boot time jumped from about 4min to about 45 minutes.  The daemon seems to be verifing the content of my cache, but in doing so it initially caused me to think the system hung on boot.

Version-Release number of selected component (if applicable):cachefilesd-0.10.2-1.el6.x86_64


How reproducible: 100%


Steps to Reproduce:
1. cache about 45G of NFS data
2. reboot
3. watch as cachefilesd performs lots of disk I/O

Actual results:
extremely slow boot

Expected results:
cache verification in the background?

Additional info:

Comment 2 RHEL Program Management 2013-10-13 23:08:03 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 3 Jan Kurik 2017-12-06 10:17:56 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/