Bug 1194239

Summary:	tracker-miner-fs is crashing on RHEL 7.1 Snaphot 3
Product:	Red Hat Enterprise Linux 7	Reporter:	jigar <jraising>
Component:	tracker	Assignee:	Matthias Clasen <mclasen>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.1	CC:	debarshir, tpelka, vrutkovs
Target Milestone:	rc	Keywords:	Tracking
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-19 07:31:40 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:
Bug Depends On:
Bug Blocks:	1133060

Description jigar 2015-02-19 11:41:15 UTC

Description of problem: The tracker-miner-fs process is crashing.There was am information on the desktop that the application had crashed. Error messages can be seen in /var/log/messages. 


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


How reproducible:Always


Steps to Reproduce:
1. Get linux-3.18.3.tar.xz from kernel.org
2. tar xvfJ linux-3.18.3.tar.xz
3. tracker-miner-fs is crashing during step 2

Actual results: Following error messages can be seen in /var/log/messages:

Jan 22 09:07:01 localhost gnome-session: (tracker-miner-fs:3126): Tracker-CRITIC
AL **: tracker_file_system_forget_files: assertion 'node != NULL' failed

Jan 22 09:07:03 localhost kernel: tracker-miner-f[3126]: segfault at 80 ip 00000
00000000080 sp 00007fffcea3efb8 error 14 in tracker-miner-fs[400000+1d000]

Expected results: No error messages should be seen.

Comment 2 Vadim Rutkovsky 2015-05-13 10:26:45 UTC

Works fine in tracker-1.2.5-2.el7.x86_64

Comment 3 Debarshi Ray 2015-05-20 12:04:43 UTC

To be clear, I don't think we can do anything in tracker to fix this kind of problems. The issue is that there is no good API offered by the Linux kernel to monitor a big directory tree. We have inotify and that is what tracker uses, but it is not ideal. Therefore, when you untar a giant tarball it eats up a bunch of inotify watches and causes things to crash.

The workaround would be to not ask tracker to index source code. Or, don't put source code in locations indexed by tracker.

Comment 8 errata-xmlrpc 2015-11-19 07:31:40 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2215.html