On 2010-08-25, at 17:04, Jan Kara wrote: >> What size is the inode ? This problem happens if the size is larger than 128 byte. (I tested at 256 byte inode.) > > Ah, that was the reason. Thanks. But looking at the implications, I'm a bit > reluctant to do the change you propose. If someone has a filesystem created > by old mkfs, he could suddently see corrupted xattrs in his lost+found > directory with the new kernel. Not that there would be a big chance this > happens but people run various strange environments... The fix to e2fsck for this issue has been around for a long time, AFAIK. It was only needed in the kernel while the broken mke2fs was in wide use, and before a fixed e2fsck was available. Cheers, Andreas -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
