This bug is the same as (or at least very similar to) upstream bug 128767 <https://rt.central.org/rt/Ticket/Display.html?id=128767>. It was due to certain disk errors being ignored, which caused corruption in the dcache hash chains that would go unnoticed for a long time (until a panic like the one in this bug report ocurred, much later).
There were a variety of different commits to track this down or fix it, the last of which is commit c8ffb8b9eefc8c2a0c6b41e3e29c0f03940a5fcf, which was in 1.6.6. The actual panic in this bug report was maybe 'fixed' a bit before that, but I'd need to go looking to get more info. Yair, if you still care about this, can I assume you haven't seen this panic in a while? I defer to Ben if he wants to close this or get confirmation, etc etc. -- Andrew Deason adea...@sinenomine.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
