FS#20832 - pacman seems to sometimes corrupt files on extraction

Attached to Project: Pacman
Opened by Ian (zerathidune) - Sunday, 12 September 2010, 23:30 GMT
Last edited by Allan McRae (Allan) - Monday, 11 October 2010, 00:20 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Xavier (shining)
Dan McGee (toofishes)
Architecture i686
Severity Medium
Priority Normal
Reported Version 3.4.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:

I was attempting to set up the xen package in AUR on i686, but two files in the package seem to get corrupted when they are extracted by pacman:

/boot/xen-4.0.1.gz
/boot/xen-syms-4.0.1

Steps to Reproduce:

build xen package on i686
cd /tmp
bsdtar -xvf /path/to/xen/package.pkg.tar.xz
cmp boot/xen-4.0.1.gz
cmp boot/xen-syms-4.0.1

The last two commands for me report :

boot/xen-4.0.1.gz /boot/xen-4.0.1.gz differ: byte 1, line 1
boot/xen-syms-4.0.1 /boot/xen-syms-4.0.1 differ: byte 5615618, line 67330

I don't know if this affects x86_64 or not as well. Both GNU tar and BSD tar seem to extract the package correctly while pacman does not.
This task depends upon

Closed by  Allan McRae (Allan)
Monday, 11 October 2010, 00:20 GMT
Reason for closing:  Works for me
Comment by Xavier (shining) - Monday, 27 September 2010, 17:54 GMT
Is this reproducible ? can you get a smaller testcase (archive) with the problem ?

I definitely cannot reproduce that problem, on x86_64, but I still find it surprising. Are you sure your hardware is perfectly ok, memory, disk ?
And your filesystem ?
Comment by Dan McGee (toofishes) - Friday, 08 October 2010, 12:58 GMT
Ping to bug opener on this- we're waiting on you.
Comment by Ian (zerathidune) - Saturday, 09 October 2010, 02:36 GMT
Sorry for the delay - life's been hectic. I was able to reproduce the issue with that archive pretty consistently when I reported this, But now I can't, even with the archive that I originally noticed it with - on any arch. Given that, I'm not sure there's much to do at this point. Could have been a number of things. hardware failure seems unlikely to me since I've seen no other issues with the machine, who knows though.
Comment by Allan McRae (Allan) - Monday, 11 October 2010, 00:20 GMT
I am closing this big as there is not much we can do given there is no way to reproduce.

Loading...