Description of problem:
I tried to manually launch abrt whilst tracker mining/indexing was switched on. abrt would fail with "disk full" errors, though df reported my disk was not full. As soon as tracker was switched off, the problem disappeared.
Version-Release number of selected component (if applicable):
Only tried once so far.
Steps to Reproduce:
1. tracker-control -s (only default miners are installed. Left it running over night to index system. It appeared to have done so as it had reached 100% indexing completed.)
2. service abrtd stop
3. abrtd -dvvv
4. Output of abrt:
abrtd: inotify_add_watch failed on '/var/cache/abrt': No space left on device
5. Because of this error, I ran df. Here is the output:
Filesystem 1K-blocks Used Available Use% Mounted on
100791728 12018816 83652912 13% /
tmpfs 2001184 956 2000228 1% /dev/shm
/dev/sda1 198337 98969 89128 53% /boot
47807384 36117772 9261096 80% /home
6. Next, I turned off the data-mining with: tracker-control -t
7. Ran abrtd -dvvv again.
8. Error no longer appears.
abrt was reporting that disk was out of space when only 13% of root was in use.
Data mining/indexing should not consume this amount of resources (if it was) or interfere with running of other programs.
(In reply to comment #0)
The following response were left by the upstream developer on the bug at GNOME bugzilla;
> abrtd: inotify_add_watch failed on '/var/cache/abrt': No space left on device
"No space left on device" is slightly inaccurate. What it really means is, you
have no more inotify watches available. You have exhausted them all.
Tracker uses MAX - 512 so you always have 512 for other applications, so
presumably some other application is using a lot of inotify watches AND you
used up all the watches in Tracker too.
> 5. Because of this error, I ran df. Here is the output:
> Filesystem 1K-blocks Used Available Use% Mounted on
> 100791728 12018816 83652912 13% /
> tmpfs 2001184 956 2000228 1% /dev/shm
> /dev/sda1 198337 98969 89128 53% /boot
> 47807384 36117772 9261096 80% /home
Yea, this has nothing to do with actual disk space.
> 6. Next, I turned off the data-mining with: tracker-control -t
> 7. Ran abrtd -dvvv again.
> 8. Error no longer appears.
That's because tracker uses a lot if watches (depending on your file system).
Are you able to provide logs from tracker-miner-fs? For details see the Logging
section of this page:
That log should tell you if you're exhausting your inotify watches or not,
which I suspect you are, in any case, there should be *some* left for your
application to operate normally unless another application uses too many too.
Created attachment 410246 [details]
Here is a copy of the tracker-miner-fs.log. Hope this helps. Cheers.
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. 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 '13'.
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 13'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 13 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.