All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joshua J. Berry" <des@condordes.net>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] COW and checksumming ioctls
Date: Sun, 22 Jun 2008 11:13:45 -0700	[thread overview]
Message-ID: <200806221113.57846.des@condordes.net> (raw)
In-Reply-To: <1214143806.10187.538.camel@think.oraclecorp.com>

[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]

On Sunday 22 June 2008 07:10:06 Chris Mason wrote:
> On Sat, 2008-06-21 at 03:27 -0400, Christoph Hellwig wrote:
> > Synthetic xattrs are a really utterly horrible interface.  Xattrs on
> > disk are nice and simple, but the Linux invention of making some up
> > on the fly, starting with the Posix ACL interface makes the
> > implementation not just utterly complicated but also confuses backup
> > programs.
>
> 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.
>
> 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.

+1 for xattrs.  From a user perspective, they're simpler than futzing around 
with special btrfs programs to set/unset attributes, and as Chris points out, 
having backup programs pick them up is a good thing.

If virtual xattrs are so complicated/messy to implement, perhaps they should 
be made simpler.  I honestly can't think of a better interface for something 
like this.

-- Josh


-- 
Joshua J. Berry

"I haven't lost my mind -- it's backed up on tape somewhere."
    -- /usr/games/fortune


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-06-22 18:13 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 [this message]
2008-06-30 18:38       ` Christoph Hellwig

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=200806221113.57846.des@condordes.net \
    --to=des@condordes.net \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.