Use debugfs so show us the full details of that inode. I don't think that can be anything but bad data written to the inode. That should not be possible unless an ext2fs bug or something else wrote bad data there, or you have a bad disk or bad memory or something like that. If e2fsck didn't find a problem with that inode, then the problem must have been introduced later by ext2fs. Or perhaps ext2fs just somehow confused itself about what was really on the disk.
_______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
