Tracker sets number of inotify watches to a ridiculously low number

Bug #1635508 reported by Mathieu Comandon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
New
Undecided
Unassigned

Bug Description

I have been trying to get Ubuntu to ship with a sane amount of inotify watches for the past few years and so far there hasn't been any progress made with that. I've noticed that Tracker increases the number of watches which is a very good thing! Unfortunately, this number is way too low to be useful on any modern desktop computer.

The current limit set by tracker is set to 65536 which is somewhat an improvement over the useless 8192 default but to be useful, and not show false error messages about full disk drives, inotify needs at least 524288 watches or better 1048576 (which is the value used by the InSync client).

The sad thing is, when kde-runtime is installed the 30-baloo-inotify-limit.conf file sets the value to 524288 but unfortunately, 't' comes after 'b' in the alphabet hence tracker overrides that nice and sane value to one that will confuse pretty much any user with cryptic and false messages about full hard drives. (WD=-1, Errno=No space left on device (ENOSPC))

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: tracker-miner-fs 1.10.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Oct 20 20:35:38 2016
InstallationDate: Installed on 2015-05-15 (525 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
SourcePackage: tracker
UpgradeStatus: Upgraded to yakkety on 2016-10-19 (1 days ago)

Revision history for this message
Mathieu Comandon (strycore) wrote :
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Debian/Bugs . If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.