> Please also make sure to test with a 3.0 fsck binary.

I can, but I'm sure the issue is not just a false alarm from fsck; I've
looked at the on-disk data with other tools (like dd seek=), and the
files are in fact corrupt, in ways that match up with the fsck gripes.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B