Bug 827504 - tracker uses up all inotify resources
tracker uses up all inotify resources
Product: Fedora
Classification: Fedora
Component: tracker (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Deji Akingunola
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-06-01 12:07 EDT by David Mansfield
Modified: 2013-07-31 18:53 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-31 18:53:13 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Mansfield 2012-06-01 12:07:47 EDT
Description of problem:
AFter starting up and logging in, without launching any other app, all but about 300 of my inotify watches are consumed (max_user_watches is 8192).  This means that apps that need to use watches, such as rhythmbox, eclipse or my own perl scripts will quickly exhaust the remaining 300 and begin to fail.  For example, tail will fail to establish a watch and resort to polling, after issuing an error message.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
(assuming you have at least 500 music folders in your rhythmbox library)
2.strace -f -o /tmp/strace.out rhythmbox 
3.examine /tmp/strace.out, see that add_watch fails at about 300
Actual results:
95% of my user alotted watches consumed before I even run an app

Expected results:
5% of my user alotted watches consumed before I even run an app

Additional info:
Comment 1 David Mansfield 2012-06-01 12:09:30 EDT
By the way, the only way to discover what process is doing this is one by one killing them until you see the watches are available again.  In this case I was able to discover tracker is the culprit.

This snippet from the internet shows which processes are using inotify:

for foo in /proc/*/fd/*; do readlink -f $foo; done | grep inotify | sort | uniq -c | sort -nr
Comment 2 Fedora End Of Life 2013-07-03 17:37:19 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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 to Fedora 17's end of life.

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 3 Fedora End Of Life 2013-07-31 18:53:17 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Note You need to log in before you can comment on or make changes to this bug.