Description of problem:
abrt version: 1.1.13
Attached file: backtrace
cmdline: /usr/bin/updatedb -f 'sysfs\nrootfs\nbdev\nproc\ncgroup\ncpuset\ntmpfs\ndevtmpfs\nbinfmt_misc\ndebugfs\nsecurityfs\nsockfs\nusbfs\npipefs\nanon_inodefs\ninotifyfs\ndevpts\nramfs\nhugetlbfs\nmqueue\nselinuxfs\nrpc_pipefs\nautofs\nfuse\nfusectl'
reason: Process /usr/bin/updatedb was killed by signal 6 (SIGABRT)
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 6.0 (Santiago)
Steps to Reproduce:
mlocate should not crash
Created attachment 494643 [details]
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
Thanks for your report. This assertion failure most likely indicates a kernel error.
Is this reproducible? (If not, perhaps it would be reproducible if you removed /var/lib/mlocate/mlocate.db .)
If this were reproducible, the last thousand lines of log files produced by
> strace -v -ff -o log /etc/cron.daily/mlocate.cron
would probably identify the specific problematic file system, directory, and directory entry.
> find / -inum 7077956
could also identify the directory: if this returns a directory, please attach the log file created by
> strace -v -o log ls path_to_that_directory
(In reply to comment #6)
> Thanks for your report. This assertion failure most likely indicates a kernel
> Is this reproducible? (If not, perhaps it would be reproducible if you removed
> /var/lib/mlocate/mlocate.db .)
> If this were reproducible, the last thousand lines of log files produced by
> > strace -v -ff -o log /etc/cron.daily/mlocate.cron
> would probably identify the specific problematic file system, directory, and
> directory entry.
> > find / -inum 7077956
> could also identify the directory: if this returns a directory, please attach
> the log file created by
> > strace -v -o log ls path_to_that_directory
I can add a workaround, but the kernel bug still needs diagnosing and fixing. Can you obtains specifics from the customer?
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.