Your message dated Mon, 23 Feb 2009 21:26:21 +0000
with message-id <[email protected]>
and subject line Probable Cause
has caused the Debian Bug report #511856,
regarding rzip: Corruption
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
511856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511856
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rzip
Version: 2.1-1
Severity: important
I had previously compressed a hard disk image with rzip with a command
simiar to the following:
rzip -k --best -o dir/disk.img.rz disk.img
This produced no error message. I attempted to unzip using a command
similar to the following:
rzip -d -o dir/disk.img disk.img.rz
This produced the error:
Bad checksum 0x3b2bfb2a - expected 0x23e76800
Fatal error - exiting
Obviously I don't know if the error is in the compression, the uncompression
or the checksum calculation but something is clearly not right and it is
refusing to continue uncompressing the file.
I am not sure how relevant this is but the original disk image is a sparse
file of about 8Gb in size. For both practical and condifentiality reasons
I can not send the file concerned but I could keep a copy for a while if
this would be helpful.
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.28-ecrins
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages rzip depends on:
ii libbz2-1.0 1.0.5-1 high-quality block-sorting file co
ii libc6 2.7-16 GNU C Library: Shared libraries
rzip recommends no packages.
rzip suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Since I reported this bug I have found a defective memory module - it
passed the POST but memtest86+ found errors. This memory fault seem
like a more likely explanation for the corruption I was seeing that a
bug particularly given the element of randomness.
--- End Message ---
