You are not logged in.
Hey,
I had a problem related to pacman today. I upgraded my system with a regular pacman -Syu command and everything seemed to go normally. However, shortly after the update my system freezed
and I had to reboot. After that reboot I couldn't start KDE anymore (mouse/keyboard didn't respond), there were some error messages on boot, too. (something about /usr/lib/libwrap.so.0 being too short, among other things).
It turned out later that hal, dbus and syslog-ng refused to start, because of various corrupted files in the filesystem.
I found out that what happened was that pacman installed corrupted packages containing size 0 files. All of the packages I upgraded in that session were corrupted. About 100 libraries in /usr/lib were broken. Luckily I was still able to read /var/log/pacman.log, and after redownloading those archives, I was able to fix my system. However, I still think that potentially this bug could have destroyed my system, because all the archives were affected, i.e. potentially all my files on my filesystem were in danger.
The only reason I was able to fix the system, was because I was still able to boot (only without X) (ok maybe there would have been another way, but still this shouldn't happen).
Is this a known issue? What caused this? I'm reporting this because the damage could have been much more severe...
Cheers
Bastian
Last edited by totsilence (2010-02-21 16:14:04)
Offline
this seems odd, doesn't pacman verify package integrity before upgrading?
have you upgraded your local pacman database since then or is that still as it was before you upgraded:
/var/lib/pacman/local/{packagename-version}/descthis file holds a %SIZE% variable, can you check those for packages you know where affected?
Last edited by stefanwilkens (2010-02-21 16:36:02)
Arch i686 on Phenom X4 | GTX760
Offline
Haven't you considered that the packages were installed correctly but were corrupted due to the unclean reboot?
Offline
this seems odd, doesn't pacman verify package integrity before upgrading?
have you upgraded your local pacman database since then or is that still as it was before you upgraded:
/var/lib/pacman/local/{packagename-version}/descthis file holds a %SIZE% variable, can you check those for packages you know where affected?
The values seem to be ok, of course I have reinstalled from clean archives now...
Haven't you considered that the packages were installed correctly but were corrupted due to the unclean reboot?
That's also a possibility, but why would my system freeze immediately after installing those packages? My theory was that one of the libraries which were needed failed and caused the system to freeze, even before the reboot. Also I ran fsck a couple of times and it didn't find any problems. It seems that those archives (and their contents) were the only corrupted files, too, so I don't know... Of course you might still be right!
Offline