From: Christoph Hellwig <hch@infradead.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Zach Brown <zach.brown@oracle.com>, Mingming <cmm@us.ibm.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] COW and checksumming ioctls
Date: Mon, 30 Jun 2008 14:38:57 -0400 [thread overview]
Message-ID: <20080630183857.GA8113@infradead.org> (raw)
In-Reply-To: <1214143806.10187.538.camel@think.oraclecorp.com>
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 :)
prev parent reply other threads:[~2008-06-30 18:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 0:26 [PATCH] COW and checksumming ioctls Mingming
2008-06-20 5:23 ` Zach Brown
2008-06-20 14:01 ` Joe Peterson
2008-06-20 13:58 ` Josef Bacik
2008-06-20 15:07 ` Joe Peterson
2008-06-20 16:37 ` Chris Mason
2008-06-21 6:07 ` Joe Peterson
2008-06-20 19:44 ` jim owens
2008-06-21 5:59 ` Joe Peterson
2008-06-21 7:27 ` Christoph Hellwig
2008-06-22 14:10 ` Chris Mason
2008-06-22 18:13 ` Joshua J. Berry
2008-06-30 18:38 ` Christoph Hellwig [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080630183857.GA8113@infradead.org \
--to=hch@infradead.org \
--cc=chris.mason@oracle.com \
--cc=cmm@us.ibm.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=zach.brown@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox