On Sun, Jun 22, 2008 at 10:10:06AM -0400, Chris Mason wrote: > The idea is that backup programs already know how to do xattrs and can > easily be changed to preserve them. Every ioctl interface we > create/make up has to be handed coded into the backup program.
Actually they don't. Because of the mess we've created with the xattr namespaces and the way e.g. ACLs are mapped into two of them they will need to special case the interesting non-user attributes. While sane backup applications already know about the inode flag word because it contains lots of useful information for the existing filesystems. > I know xattrs are ugly, but we need to weigh the cost of the perfect > interface with the availability of a common one. Dave Chinner had > talked about using xattrs to control file behavior in XFS as well, not > sure if that ever happened. I think I've successfully talked him out of it :) -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
