From: Tim Cwik <tcwik@shuttleamerica.com>
To: 9fans@cse.psu.edu
Subject: [9fans] vmware image corrupt?
Date: Wed, 15 May 2002 11:27:25 -0400 [thread overview]
Message-ID: <20020515112725.E2870@phoenix.shuttleamerica.com> (raw)
Has anyone else had problems decompressing the vmware image from the
additional software page
of the plan9 site?
Using bunzip2 version 1.0.1 23-June-2000 on redhat linux 7.2, I get
bunzip2: Data integrity error when decompressing.
Input file = vmware.tar.bz2, output file = vmware.tar
Using the -tvv as suggested in the error message, I get
vmware.tar.bz2: [1: huff+mtf rt+rld]
[2: huff+mtf rt+rld]
[3: huff+mtf rt+rld]
[4: huff+mtf data integrity (CRC) error in data
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
Using bzip2recover and bzip2 -t on the individual blocks gives:
rec0083vmware.tar.bz2: [1: huff+mtf rt+rld]
ok
rec0084vmware.tar.bz2: [1: huff+mtf rt+rld]data integrity (CRC)
error in data
rec0085vmware.tar.bz2: [1: huff+mtf rt+rld]
ok
rec0086vmware.tar.bz2: [1: huff+mtf rt+rld]data integrity (CRC)
error in data
rec0087vmware.tar.bz2: [1: huff+mtf rt+rld]data integrity (CRC)
error in data
rec0088vmware.tar.bz2: [1: huff+mtf rt+rld]
ok
rec0089vmware.tar.bz2: [1: huff+mtf rt+rld]data integrity (CRC)
error in data
rec0090vmware.tar.bz2: [1: huff+mtf rt+rld]data integrity (CRC)
error in data
rec0091vmware.tar.bz2: [1: huff+mtf rt+rld]
ok
rec0092vmware.tar.bz2: [1: huff+mtf rt+rld]
ok
rec0093vmware.tar.bz2: [1: huff+mtf rt+rld]data integrity (CRC)
error in data
for blocks 4, 8, 12, 49, 80, 84, 86, 87 ...
This problem has occured on 3 separate download attempts.
Any thought?
Tim
next reply other threads:[~2002-05-15 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 15:27 Tim Cwik [this message]
2002-05-15 17:38 ` Vladimir G. Ivanovic
2002-05-16 18:31 ` Tim Cwik
2002-05-15 18:31 rsc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020515112725.E2870@phoenix.shuttleamerica.com \
--to=tcwik@shuttleamerica.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).