dpkg hangs with no information on corrpted /var/lib/dpkg/info/*.list file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dpkg (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: dpkg
I'm struggling with a filesystem that was corrupted by a kernel problem (reported seperately). Some files did not survive an fsck correctly:
$ sudo ls -ld /var/lib/
p----w---- 1 proxy 4122 0 1970-01-10 16:48 /var/lib/
I don't expect dpkg to be able to do anything with this, but I would like to get some debugging information when trying to track this down. As it was, it was hanging on "(Reading database ..." with no other information available, no matter what level I set the debugging to.
It would be nice if dpkg could verify that a file was un-readable or not actually a file, etc before reading it.
Alternatively, a debugging level could be added so that every file under /var/lib/dpkg/info is printed as it is accessed. In this way, it would be easier to track down the problem since output would stall out on the bad file.
I have prepared a small fix for this and queued it for later merge in upstream dpkg.