[SOLVED] ldconfig executable filled with zeroes

elifarley · 2010-10-18 23:44:00

After upgrading glibc via pacman -Sf, ldconfig contains only zeroes. Unpacking glibc with tar (from the same archive) works just fine.

I wonder what pacman does differently than tar when it comes to extracting files from a tar archive.

Where in pacman's source code should I look in order to understand this?

Nothing interesting appeared on /var/log/pacman

I'm using a recently updated Arch64 install (about a week old).

Thanks!

Last edited by elifarley (2010-11-07 14:08:44)

toofishes · 2010-10-18 23:53:41

What happens when you extract with bsdtar (a frontend to libarchive, the tar library pacman uses)?

Allan · 2010-10-19 00:32:13

elifarley wrote:

After upgrading glibc via pacman -Sf

Bad...

Did you run out of disk space?

elifarley · 2010-10-20 19:29:23

toofishes: Before reading your suggestion to use bsdtar, I reinstalled some packages using Arch's installation CD, so I didn't have the chance to test it. Will keep that in mind for the next time, thanks!

Allan: I believe I didn't run out of disk space.

Anyway, all my problems started after a 'pacman -Syu'. The operation was interrupted due to a segmentation fault. I retried it, and the segmentation fault wouldn't go away. After trying once again, I saw a weird message like 'XFS in-memory data structures corrupt, mounting file system in read-only mode' regarding my /usr partition. I performed an 'xfs_check', but no errors could be found. I was using Arch 32 bits up to this point.

Then I decided to reformat the /usr partition and re-install Arch (amd_64 this time), so as to have all system files rewritten, removing any possible file corruption left.
First, I created a list of installed packages with 'comm -23 <(pacman -Qeq) <(pacman -Qmq) > pkglist'. Then, I performed a basic installation to get the system working again.
After booting into the newly installed system, I tried to re-install the packages listed in pkglist (pacman -S $(< pkglist)). Doing this somehow filled ldconfig with zeroes.
To fix this, I rebooted with the Arch CD to reinstall glibc. Then I split the 'pkglist' file in chunks of 30 - 40 packages each, trying to pin-point the problem. Much to my surprise, I was able to install all chunks without corrupting ldconfig.

Now I only have to reinstall KDE, X.org and some other big packages to get my system back to normal.

Having my /etc folder tracked by Mercurial (with a few ignored files) made it really easy to get the system configuration to its previous state.

Arch Linux

#1 2010-10-18 23:44:00

[SOLVED] ldconfig executable filled with zeroes

#2 2010-10-18 23:53:41

Re: [SOLVED] ldconfig executable filled with zeroes

#3 2010-10-19 00:32:13

Re: [SOLVED] ldconfig executable filled with zeroes

#4 2010-10-20 19:29:23

Re: [SOLVED] ldconfig executable filled with zeroes

Board footer