On Sun, Apr 07, 2013 at 01:42:18PM -0500, Eric Sandeen wrote: > e2fsck thinks that this: > > # touch mnt/testfile1 > # setfattr -n "user.test" mnt/testfile1 > > results in a filesystem with corruption: > > Pass 1: Checking inodes, blocks, and sizes > Extended attribute in inode 12 has a value size (0) which is invalid > Clear? yes > > but as far as I can tell, there is absolutely nothing wrong with > a 0-length value on an extended attribute. Just remove the check. > > Reported-by: David Shaw <dshaw@xxxxxxxxxxxxxxx> > Reported-by: Harald Reindl <h.reindl@xxxxxxxxxxxxx> > Addresses-Red-Hat-Bugzilla: #557959 > Signed-off-by: Eric Sandeen <sandeen@xxxxxxxxxx> Thanks, applied. It turns out that 0-length values applied for xattrs stored in external xattr blocks. 0-length xattrs were only only getting prohibited for in-inode xattrs. - Ted -- 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
