TKLBAM restore gets stuck when insufficent HDD space
Bug #870364 reported by
Jeremy Davis
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| TurnKey Linux |
Fix Released
|
Medium
|
Liraz | ||
Bug Description
Christian reports in the forums that TKLBAM restore gets stuck when there is insufficient HDD space available. It seems that TKLBAM restore temporarily stores files in /tmp during restore process - meaning that HDD needs to be bigger than than the size of restored files (how much bigger?) Currently TKLBAM does not seem to check for this nor give a clear error message when it occurs.
See here: http://
| Changed in turnkeylinux: | |
| status: | New → Confirmed |
Revision history for this message
| Jeremy Davis (jedmeister) wrote | #1 |
| Changed in turnkeylinux: | |
| assignee: | nobody → Liraz (liraz-siri) |
Revision history for this message
| Jeremy Davis (jedmeister) wrote | #2 |
Revision history for this message
| Jeremy Davis (jedmeister) wrote | #3 |
| Changed in turnkeylinux: | |
| status: | Confirmed → Fix Released |
| importance: | Undecided → Medium |
To post a comment you must log in.
This bug has been sort of resolved. It is no longer an issue with AWS/EC2 instances as it maps /tmp to /mnt/tmp (which has tons of space). But as TKLBAM is still not check for available space on the filesystem, it remains a potential issue for VM instances (and HDD installed instances with very small primary hard drives).