Bug 1382251

Summary:	Deadlock when DM starts
Product:	[Fedora] Fedora	Reporter:	Miroslav Suchý <msuchy>
Component:	cachefilesd	Assignee:	David Howells <dhowells>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	24	CC:	dhowells, steved
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-08 19:20:30 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:

Description Miroslav Suchý 2016-10-06 06:32:56 UTC

Description of problem:
I have /home NFS mounted. When I enable cachefilesd, then I am able to read content of my home and read files. However, when I start display manager (DM) (I tried KDE, Gnome, LXQt) then system freeze. I am not even able to change VT. It is complete freeze. I suspect that it is because DM starts reading a lots of small files.
The fact that cachefilesd cache directory reside on very fast SSD disk (in M2 slot) can play the role (maybe there is some race condition?).

Anyway, because the system freeze, there is no coredump, nor I can run strace. If you can suggest me how I can debug it, then I'm willing to provide more data.

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

How reproducible:
deterministic

Steps to Reproduce:
1. NFS mount /home, put cache on fast SSD disk
2. enable cachefilesd
3. log into display manager

Actual results:
freeze of system

Comment 1 Fedora End Of Life 2017-07-25 23:22:44 UTC

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora  'version'
of '24'.

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.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 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  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

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.

Comment 2 Fedora End Of Life 2017-08-08 19:20:30 UTC

Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.