Bug#382394: have you *ever* used 2.6.17-(<5)

[dann frazier <dannf@debian.org>]

hey Giuseppe,
  It is quite possible (we have seen this in other reports) that the
corruption occurred while you were running an earlier 2.6.17 build and
got written to disk.  Then, when you were running 2.6.17-5, you
tripped over this corruption causing the problems you described.

Can you confirm whether or not you had previously mounted this
partition under a 2.6.17 kernel earlier than 2.6.17-1? You should be
able to check /var/log/dpkg.log* to see if you had installed one.

-- 
dann frazier