wal-e: Insufficient temporary space leads to unclear errors on backup-push
When there is insufficient temporary space (/tmp) during a backup-push IOError 32 (broken pipe) is raised. This issue may not be limited to backup-push.
Root cause
Insufficient /tmp space
Mitigation
- Allocate more
/tmpspace. (May not be possible in some environments) - Perform
backup-pushwith--pool-size=1to resolve higher space requirements from default of multiple workers multiplying the /tmp load.
Fixes
- Document the above.
--pool-sizedoes not seem to be documented anywhere, I just happened to come across it while diagnosing this issue. I hope that this issue will help others encountering this problem. - Check for available temporary space for each worker before starting and error out gracefully.
- Allow the user to specify a temporary path to override the default.
- (Minor) If possible, determine if insufficient space (IOError 12) is the root cause for the broken pipe and error out gracefully.
About this issue
- Original URL
- State: open
- Created 11 years ago
- Comments: 18 (13 by maintainers)
Hi, It looks like this issue isn’t resolved, and TMPDIR workaround isn’t working as well - temp files are still being created in /tmp, despite pointing TMPDIR to another location. pool-size isn’t a solution, because my /tmp partition is smaller, than default part size (1G) - is it possinle to decrease part size?