On Jun 26, 2008 09:04 -0500, Dave Kleikamp wrote:
> Honestly, I can see XATTR used generically, even though most filesystems
> don't store the XATTR as a tree. (jfs stores it in a single extent.)
> SYNC really doesn't look like it belongs, and it's only there so that
> the new ioctl acts like the xfs ioctl.
I think the use of "tree" in the XATTR description is a bit misleading.
It doesn't really matter how the xattrs are layed out on disk, or how
they are addressed internally to the filesystem. The "extents" returned
by FIEMAP will just be a list of {physical,logical start}+length ranges
that map one (or more) locations on disk the xattrs for this inode are
stored.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
