package mysql-server-5.0 5.1.30really5.0.75-0ubuntu10.2 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive

[Paul Whipp]

Yes, yet another corrupt package breaks as the package management tries to load it.

Please look at automatically using checksums to verify downloaded packages so that these bugs can stop cluttering your system and breaking peoples desktop systems when they do updates.

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage: corrupted filesystem tarfile - corrupted package archive
NonfreeKernelModules: nvidia
Package: mysql-server-5.0 5.1.30really5.0.75-0ubuntu10.2
SourcePackage: mysql-dfsg-5.0
Title: package mysql-server-5.0 5.1.30really5.0.75-0ubuntu10.2 failed to install/upgrade: corrupted filesystem tarfile - corrupted package archive
Uname: Linux 2.6.28-17-generic i686

[Scott Moser (smoser)]

Are you implying that the .deb file was downloaded incorrectly and that wasn't checked? if so, this is definitely not a bug with mysql.

[Paul Whipp (paul-whipp)]

Yes, I believe that is what happened. I live in a rural area and have a flaky but fairly fast internet connection (given my distance from the exchange 150kb is fast) and I often see this kind of error or worse when I attempt an upgrade.

Sometimes it takes quite a few attempts (I repeated the mysql server deb download this morning and its worked).

This time the consequences were not serious because the failure appears to have been 'clean' but on many occasions the attempt to load the corrupt file results in system corruption that can sometimes be a real headache to fix.

A built in checksum on the deb files before an attempt is made to load them (ideally with the higher level applications like synaptic giving the option to reload the deb) would eliminate this problem. I don't know but I am willing to bet there are an awful lot of bugs raised because of this problem. I know I get the "submit a bug" option so often because of it that I rarely file it.

This one was particularly frustrating (I depend on mysql-server a lot and it was a big file) so I thought I'd flag it again. If its coming to the wrong group then perhaps the reporting process for bugs can be changed so that corrupt downloaded file errors are caught and punted somewhere else?

[Scott Moser (smoser)]

I'm moving this to 'apt', while I would have thought that this was already done.

[Michael Vogt (mvo)]

Thanks for your bugreport.

Apt does use checksums while downloading. The check is performend on the data that is recived from the network and gets into the buffer. Apt does not re-check if the buffer -> disk was write was correct. The errors we have seen that look similar to this one have been file system corruption or bad RAM. Can you please run a memtest and a filesystem check to ensure that the machine is fine?

[Paul Whipp (paul-whipp)]

Michael,

Thank you for being the first person to give me some clear information on this! Knowing that the checksum is done (which seemed logical) firmly points the finger at my system as you suggest.

Its strange that the error seems almost 100% repeatable with large updates and almost never occurs outside of them although I have had a couple of random restarts and seen some one bit errors in other large files such as big sql dumps.

I have run memtest and not got any errors but I'll run it again for a decent period and see what turns up.

I've scanned the drives and not found anything but I'm not sure how to ensure that the swap space gets checked properly - should I worry about that too?

Thanks for your help. It does look as though this is not a bug after all.

[Victor Vargas (kamus)]

@Paul, any news about this issue?

[Paul Whipp (paul-whipp)]

In my case issues like this lead to a long period of diagnosing what was
wrong with my system. I was getting these corruptions on about 1 in 20
upgrades. My machine also crashed about once a month (not always fatally -
sometimes just Firefox etc.).

Memory diagnostics did not show anything until I ran them for 48 hours when
they showed a single failure. I bought new memory and installed it. I have
never had a corrupt tarfile issue since then.

I now believe the cause of the corrupt file was actually a hardware fault on
my system.

Regards,
Paul Whipp

Office: 07 3103 2894
Mobile: [phone]

Do more business with your website! <http://www.paulwhippconsulting.com.au>

Joomla, Magento, PHP and MySQL web application
developer<http://www.paulwhippconsulting.com.au/>

On 9 September 2010 08:06, Kamus <email address hidden> wrote:

> @Paul, any news about this issue?
>
> ** Changed in: apt (Ubuntu)
> Importance: Undecided => Low
>
> --
> package mysql-server-5.0 5.1.30really5.0.75-0ubuntu10.2 failed to
> install/upgrade: corrupted filesystem tarfile - corrupted package archive
> https://bugs.launchpad.net/bugs/520170
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “apt” package in Ubuntu: Incomplete
>
> Bug description:
> Yes, yet another corrupt package breaks as the package management tries to
> load it.
>
> Please look at automatically using checksums to verify downloaded packages
> so that these bugs can stop cluttering your system and breaking peoples
> desktop systems when they do updates.
>
> ProblemType: Package
> Architecture: i386
> DistroRelease: Ubuntu 9.04
> ErrorMessage: corrupted filesystem tarfile - corrupted package archive
> NonfreeKernelModules: nvidia
> Package: mysql-server-5.0 5.1.30really5.0.75-0ubuntu10.2
> SourcePackage: mysql-dfsg-5.0
> Title: package mysql-server-5.0 5.1.30really5.0.75-0ubuntu10.2 failed to
> install/upgrade: corrupted filesystem tarfile - corrupted package archive
> Uname: Linux 2.6.28-17-generic i686
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/apt/+bug/520170/+subscribe
>

[Launchpad Janitor (janitor)]

[Expired for apt (Ubuntu) because there has been no activity for 60 days.]