kernel.org source seems to be corrupted

ErrorBound · 06-27-2006, 07:38 PM

Hi,
first I should say that I can unzip both .tar.gz and .tar.bz2 without problems normally.

However, trying to unzip the kernel sources from kernel.org, with gzip I get,

# gunzip linux-2.4.26.tar.gz

Code:

gunzip: linux-2.4.26.tar.gz: invalid compressed data--crc error
gunzip: linux-2.4.26.tar.gz: invalid compressed data--length error

or with bzip2,

# bunzip2 linux-2.4.26.tar.bz2

Code:

bunzip2: Data integrity error when decompressing.
...
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

# bzip2 -tvv linux-2.4.26.tar.bz2

Code:

...
[27: huff+mtf data integrity (CRC) error in data

I've searched and searched and haven't found anything like this before. It does the same thing on both machines I've tried (xubuntu dapper, debian sarge), and I seem to get the same errors with different kernel versions, not only 2.4.26.
Quite confused,

pljvaldez · 06-27-2006, 07:46 PM

Perhaps your download had an error. Did you try tar -xvjf linux-2.4.26.tar.bz2?

ErrorBound · 06-27-2006, 08:20 PM

on the debian machine, tar -xvjf linux-2.4.26.tar.bz2 outputs a long list of source files, and ends with

Code:

linux-2.4.26/include/asm-alpha/core_apecs.h

bzip2: Data integrity error when decompressing.
...
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

On the ubuntu machine, every line that is output has the name of the source file, then

Code:

Cannot change ownership to uid 573, gid 573: Operation not permitted

also, i've downloaded the source many,many times, so if the download had an error, they have all had errors. I can't get my head around this one.

Daws · 06-27-2006, 08:41 PM

Quote:

bzip2: Data integrity error when decompressing.

This would suggest it is in fact a corrupted archive, I tried to uncompress the same file without problems so it seems it may have been corrupted during download.

Quote:

Cannot change ownership to uid 573, gid 573: Operation not permitted

In this case try passing the --no-same-owner option. This won't make a difference unless you were extracting as root.

Hope it helps

ErrorBound · 06-27-2006, 09:02 PM

Thanks for the help. It seems that if I do tar -xjvf as a regular user instead of as root, the extractiong works fine. This is on the debian machine, with the same file that was "corrupted" when I tried to extract as root. Oh well, I don't understand, but I'll take it and run anyway if it works...

ErrorBound · 06-27-2006, 09:14 PM

maybe I just have a really nutty machine -- tried copying the unzipped directory over to /usr/src:

Code:

cp -r linux-2.4.26 /usr/src

which somehow crashes, and gives a segmentation fault. Now the machine boots partially, mounts the file system read-only, and asks for a root password to perform maintenance, but the keyboard isn't recognized.

This thing is driving me nuts.

Daws · 06-27-2006, 09:59 PM

Basically if you extract as root the default behaviour is for files inside a tar archive to retain the same UID and GID as when they were packed. In this case this kernel's files were owned by a user and group with id 573. But on your machine there is no user or group with a numeric id of 573: hence the operation is not permitted.

As for your other problem I'm afraid I have no idea. Sorry

ErrorBound · 06-28-2006, 12:23 PM

Thanks for the help again, I've solved it now. This is a machine that was given to me for free and all sorts of things were giving me weird errors. I tried taking out one of the memory sticks and now everything works fine. It was either bad or mismatched memory.