From: Dave Chinner <david@fromorbit.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Richard Yao <ryao@gentoo.org>,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Subject: Re: Making an interface for alternative data streams
Date: Wed, 23 Mar 2016 09:50:18 +1100 [thread overview]
Message-ID: <20160322225018.GV11812@dastard> (raw)
In-Reply-To: <20160322215232.GK4083@fieldses.org>
On Tue, Mar 22, 2016 at 05:52:32PM -0400, J. Bruce Fields wrote:
> On Wed, Mar 23, 2016 at 08:29:31AM +1100, Dave Chinner wrote:
> > If you want additional seekable data streams, then come up with a
> > filesystem namespace method of addressing these alternate data
> > streams as *separate files containing data*. That's all an ADS is -
> > a namespace hack to address multiple data files through a single
> > file name. That's the problem that needs solving and it has nothing
> > to do with xattrs.
>
> There was some thread about this years ago. Looking... "silent semantic
> changes with reiser4" or "possible design issues for hybrids" look like
> the relevant threads.
>
> One good starting point might be:
>
> http://mid.gmane.org/20040826212853.GA21964@parcelfarce.linux.theplanet.co.uk
>
> Don't know how out of date that might be now.
Not sure it is the same issue - that looks like auto-bind-mount
stuff. There are some relevant questions though, like "directory
over file" semantics and implications...
But we have covered this ground before, and at LSF/MM summits, too.
historically it has been made pretty clear that xattrs are not
something that can be used for alternate data streams. I think ADS
is primarily a namespace and API problem - that needs to be sorted
out first, and then what filesytems need to implement will be
obvious.
Perhaps overlayfs is a good place to start prototyping such
functionality as there is an abstraction between the presented
namespace and the underlying storage of the data....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2016-03-22 22:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 18:11 Making an interface for alternative data streams Richard Yao
2016-03-21 18:18 ` Christoph Hellwig
2016-03-21 18:51 ` Richard Yao
2016-03-21 19:17 ` Richard Yao
2016-03-21 20:19 ` Richard Yao
2016-03-21 20:40 ` J. Bruce Fields
2016-03-21 22:36 ` Theodore Ts'o
2016-03-21 22:48 ` Cedric Blancher
2016-03-22 0:12 ` J. Bruce Fields
2016-03-22 1:02 ` Richard Yao
2016-03-22 2:21 ` Richard Yao
2016-03-22 16:15 ` Richard Sharpe
2016-03-22 20:08 ` J. Bruce Fields
2016-03-22 20:13 ` Richard Sharpe
2016-03-22 20:32 ` J. Bruce Fields
2016-03-22 21:42 ` Jeremy Allison
2016-03-23 4:13 ` Steve French
2016-03-23 4:19 ` Steve French
2016-03-23 14:45 ` Steve French
2016-03-23 17:01 ` Jeremy Allison
2016-03-23 17:01 ` Jeremy Allison
2016-03-23 17:16 ` Steve French
2016-03-23 15:16 ` J. Bruce Fields
2016-03-22 2:01 ` Richard Yao
2016-03-22 21:29 ` Dave Chinner
2016-03-22 21:52 ` J. Bruce Fields
2016-03-22 22:50 ` Dave Chinner [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=20160322225018.GV11812@dastard \
--to=david@fromorbit.com \
--cc=bfields@fieldses.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=ryao@gentoo.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.