Bug 1204464
Summary: | recollindex must use /var/tmp by default | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Richard Z. <rz> |
Component: | recoll | Assignee: | Terje Røsten <terje.rosten> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | rz, terje.rosten |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | recoll-1.20.6-1.fc22 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-05-19 16:23:45 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: |
Description
Richard Z.
2015-03-22 10:12:25 UTC
/tmp is set to tmpfs with size = (total RAM) / 2 For low end systems /tmp might be too small, you can disable /tmp as tmpfs feature with: systemctl mask tmp.mount See: http://fedoraproject.org/wiki/Features/tmp-on-tmpfs There is no limit to the size of tarballs that recollindex will try to unpack and index so it could fail even on much larger systems. Also, somewhere I read that programs should not assume that more than 1GB is available? What happened in my case: recoll sees a file "samsung32.image.bz2" which is a compressed image of a 32GB MicroSDHC card. Recoll will hapilly uncompress it in /tmp. Apparently this could bring down even high end machines if done on tmpfs and there is no limit how much space recoll may need. Meanwhile upstream says that there is the (currently undocumented) $RECOLL_TMPDIR and wont fix it. I am not even sure if /var/tmp is suitable, mine is on root and does not have terrabytes of storage. On my systems /var is far less than 32GB any way, it's ~ 5GB. I don't see any quick fix here. Using /tmp as default seems sane to me. recoll-1.20.6-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/recoll-1.20.6-1.fc20 recoll-1.20.6-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/recoll-1.20.6-1.fc21 recoll-1.20.6-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/recoll-1.20.6-1.fc22 Package recoll-1.20.6-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing recoll-1.20.6-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-7819/recoll-1.20.6-1.fc20 then log in and leave karma (feedback). recoll-1.20.6-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. recoll-1.20.6-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. recoll-1.20.6-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. |