On Sat, 05 Feb 2005 15:20:00 +0100, Andreas Gruenbacher wrote: >On Sat, 2005-02-05 at 13:39, Mikael Pettersson wrote: >> [...] It does not explain why 2.6 allocated >> the xattr blocks in the first place; as I wrote initially, I >> have disabled the xattrs stuff: >> >> CONFIG_EXT3_FS=y >> # CONFIG_EXT3_FS_XATTR is not set > >The filesystem in question must have been used with a kernel that was >xattr aware once. You could also have been using ext2. Maybe you ran >selinux at some point, or similar. Can you boot into a kernel with >CONFIG_EXT3_FS_XATTR enabled, and ``getfattr -m- -d -R .'' on the >filesystem in question? This gives you a full xattr dump.
Done. According to that command, there are no xattrs anywhere on any of the affected file systems. So it seems my self-compiled xattr-disabled 2.6 kernels aren't to blame. That leaves either the FC2 or FC3 installer kernels: one of them must have created the xattrs. I don't know why/when they were leaked, but this is consistent with the fact that I've only seen fsck complain about the xattr blocks once on any given file system. Sorry about the false alarm. /Mikael - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
