Menu
▾
▴
#53 File Corruption.
here's the deal..
root@cimmeria-uml:~# md5sum linux-2.4.20.tar.bz2
c439d5c93d7fc9a1480a90842465bb97 linux-2.4.20.tar.bz2
root@cimmeria-uml:~# tar xjf linux-2.4.20.tar.bz2
bzip2: Data integrity error when decompressing.
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become
corrupted.
You can use the -tvv option to test integrity of such
files.
You can use the `bzip2recover' program to *attempt* to
recover
data from undamaged sections of corrupted files.
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
root@cimmeria-uml:~# md5sum linux-2.4.20.tar.bz2
a4b55413bd21fa8f77a9fb71e2491214 linux-2.4.20.tar.bz2
Nothing was done in between, and they are all
subsequent commands. The original tarball transferred
is correct and whole, and the md5sum at the top is the
correct md5sum.
The host is a RH9 box running a self compiled 2.4.20
SMP kernel.
The UML is running the 2.4.20-6um patch, with an ext3
filesystem.
This can be reproduced repeatedly, on this and other
host boxes.
More info can be given as requested
Thanks,
Eric Andresen
eandres@elvis.mars.asu.edu
480-965-0993
Logged In: YES
user_id=687610
I have narrowed down to what causes this. Running the kernel
with mem=2048M (with HighMem compiled in) will show these
problems. Running the same kernel with mem=256M (highmem
still compiled in) and the problems disappear.
-- Eric Andresen
Logged In: NO
hi!
please do the same test with another filesystem.
i use reiserfs on linux-2.6.0-test11-um - no problems here.
tested this on a heavily i/o stressed system with two running
uml`s in parallel, doing the following inside of them:
while true; do cp test test.new;sync;md5sum test.new;cp
test.new test;done
md5sums didn`t change - i let this run ~1h.
when i find some time i will compile a kernel with ext3 and
test that again.
regards
roland
Logged In: NO
oh - sorry - didn`t see that there already was a answer by
yourself. sourceforge pages aren`t very clearly arranged.
:D
i have no highmem support compiled in, but perhaps it is
worth a try with another filesystem, though?
so one can track down, if this is a highmem<->ext3 problem
or a more general highmem problem.