Univention Bugzilla – Bug 39991
checks for free space seem to be too small
Last modified: 2015-12-02 15:03:46 CET
An update of an EC2 instance with default software downloaded 118MB archives and wanted to use ~225 MB extra space on that system after upgrade. So around 350 MB are required for an update.
Since the EC2 instance uses only one large filesystem for everything and the preup.sh checks for 500MB free space on /, the update seem to barely fit (only 150MB spare space).
If extra software (worst case: *-dbg or *-dev package) is installed, that check will falsely pass and the update might crash in a disk full scenario.
We will adjust the preup.sh directly with the announce.
modified/singed 4.1 preup (500MB archiv, 1500 MB /)
not yet copied to svn
Test instance (with OX) with one large rootfs and no subpartitions used up to
491 MB disk space during the update. So I think 1,5GB is ok.
updated univention-updater in errata4.1-0
(In reply to Felix Botner from comment #4)
> yaml: 2015-11-19-univention-updater.yaml
Advisory is now: univention-updater.yaml
Another test case used also ~500 MB max during update.
→ OK: Code change