GNOME Bugzilla – Bug 406250
Beagle does not handle 100% full /tmp gracefully
Last modified: 2018-07-03 09:50:15 UTC
I upgraded to version 0.2.16 Beagle. Then as usual I ran: # BEAGLE_EXERCISE_THE_DOG=1 beagled --bg --debug --replace so it would get the new indexes built up. All went well until I noticed that my /tmp partition was full and that it stayed that way. /tmp was full of *.tmp files created by Beagle. It was indexing a directory full of *.iso files. Normally these /tmp/*.tmp files come and go but in this case they got stuck. I didn't look in the code but I'd bet the filesystem full exception jumps past a tmp file delete. And because Beagle left those files in /tmp, it stayed full, causing all further indexing events to fail. I got past the problem by increasing /tmp's tmpfs to 2 GB and allowing it to swap like mad. On a side note, is it *really* necessary to copy unpacked files into /tmp? It seems a streaming decompression would work better.
Unfortunately SharpZLib doesnot offer a stream from a compressed stream. In general it is a tough thing to do, since you can archives inside archives inside archives ... and so on.
Beagle is not under active development anymore and had its last code changes in early 2011. Its codebase has been archived (see bug 796735): https://gitlab.gnome.org/Archive/beagle/commits/master "tracker" is an available alternative. Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect reality. Please feel free to reopen this ticket (or rather transfer the project to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the responsibility for active development again.