Public bug reported:
Binary package hint: partimage
This is probably an upstream problem in partimage, rather than a Dapper
problem.
Partimage 0.6.4 shipped with Dapper fails to read image files which it
creates if the gzip compression option is selected. It save the
partition into files with names such as hda5saved.000, whether the gzip
option is selected or not.
When attempting to restore a partition from a file saved with the gzip
option, partimage gives an error message "Invalid compression level for
hda5saved.000". It gives this error during command line or interactive
restore operations, or in response to an imginfo operation.
Luckily, there is a workaround:
If the saved file is less than 2GB in size, then simply renaming it as
hda5saved.gz will fix the problem. Then both restore and imginfo
operations will work correctly.
If the saved file exceeds 2GB in size, then an additional step is necessary.
The saved file must be uncompressed and piped to stdin of partimage (as root):
gunzip -c hda5saved.gz | partimage imginfo stdin
gunzip -c hda5saved.gz | partimage restore /dev/hda5 stdin
So it seems that there are two aspects to the problem. One is
inconsistent file naming assumptions between the save operation and the
restore or imginfo operations. The second is using a file write which
can handle large files, but using a file read which is limited to 2GB
per file.
- John.
** Affects: partimage (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
--
partimage cannot read image files it created (workaround exists)
https://launchpad.net/bugs/50810
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
