RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

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

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.

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