Bug 991524 - Evolution relies on /tmp for backup/restore resulting in tmpfs breakage
Evolution relies on /tmp for backup/restore resulting in tmpfs breakage
Status: CLOSED DUPLICATE of bug 981712
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
Depends On:
Blocks: F18TmpOnTmpfs
  Show dependency treegraph
Reported: 2013-08-02 12:19 EDT by Steevithak
Modified: 2013-08-05 03:33 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-08-05 03:33:20 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Steevithak 2013-08-02 12:19:14 EDT
Description of problem:
It is not possible to restore an Evolution backup created on F18 to my F19 box because Evolution apparently relies on the use of the /tmp directory for creating and unpacking archives. Fedora 19 has added a severe size limit to /tmp (2GB on my install) that prevents the creation or restoration of average to large sized email archives by Evolution. It attempts the restore process but dies partway through without providing an suitable error message.

Version-Release number of selected component (if applicable):

How reproducible:
always for archives that decompress to sizes larger than allowed by the new /tmp limit

Steps to Reproduce:
1. Create a large email backup on F18 
2. Move archive to F19 and attempt to restore

Actual results:
Restore process dies when space on /tmp is exhausted but user is not given an error message

Expected results:
1. /tmp should not have a tiny size limit when there's plenty of disk space
2. if /tmp has to be limited, Evolution should use an alternate tmp area
3. if neither is possible, Evolution should produce a suitable error message to describe why the restore process failed.

Additional info:
Comment 1 Milan Crha 2013-08-05 03:33:20 EDT
Thanks for a bug report. This was filled as bug #981712, thus I mark this as a duplicate of it. From the investigation there, the problem might be with gzip, relying on /tmp - evolution doesn't influence this at all (cat it?).

*** This bug has been marked as a duplicate of bug 981712 ***

Note You need to log in before you can comment on or make changes to this bug.