From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Anand Avati <aavati@redhat.com>
Cc: "J. Bruce Fields" <bfields@redhat.com>,
Ric Wheeler <rwheeler@redhat.com>,
Trond.Myklebust@netapp.com, linux-nfs@vger.kernel.org,
Steve Dickson <steved@redhat.com>
Subject: Re: Fwd: Re: XATTRs in NFS?
Date: Tue, 29 Oct 2013 01:39:27 +0100 [thread overview]
Message-ID: <1383007167.8774.52.camel@heisenberg.scientia.net> (raw)
In-Reply-To: <526EFFCC.2060506@redhat.com>
I might add a similar use case which we have at the faculty respectively
the local supercomputing centre:
What we have there is big cluster filesystems (used to be Lustre but
nowadays I think they use GPFS).
There are custom (i.e. local) applications where XATTRs are used to
attach some metadata to files, which works fine in these cluster
filesystems since they have native support.
Now what they sometimes do (AFAIU) is, export the cluster fs via NFS, to
nodes which don't have support for the cluster fs itself (sometimes the
OS is simply too old, but one common use case is also, that they simply
don't allow direct mounts outside of e.g. the super computer).
At that point, NFS looses the XATTRs.
Cheers,
Chris.
next prev parent reply other threads:[~2013-10-29 0:39 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 20:37 XATTRs in NFS? Christoph Anton Mitterer
2013-10-24 8:45 ` Myklebust, Trond
2013-10-24 14:13 ` Christoph Anton Mitterer
2013-10-24 14:32 ` Myklebust, Trond
2013-10-24 15:07 ` Simo Sorce
2013-10-24 15:11 ` Myklebust, Trond
2013-10-24 15:16 ` Simo Sorce
2013-10-24 15:23 ` Jeff Layton
2013-10-24 15:29 ` Matt W. Benjamin
2013-10-24 15:53 ` Myklebust, Trond
2013-10-24 16:10 ` Christoph Anton Mitterer
2013-10-24 15:27 ` Myklebust, Trond
2013-10-24 16:01 ` Christoph Anton Mitterer
2013-10-24 16:30 ` Myklebust, Trond
2013-10-24 17:22 ` Christoph Anton Mitterer
2013-10-25 14:08 ` J. Bruce Fields
2013-10-25 15:26 ` Ric Wheeler
2013-10-25 15:32 ` Chuck Lever
2013-10-26 18:00 ` Christoph Anton Mitterer
2013-10-26 13:20 ` Myklebust, Trond
[not found] ` <OF01D9818B.36018C0F-ON88257C10.00608BC0-88257C10.006139C6@LocalDomain>
2013-10-26 17:46 ` Marc Eshel
2013-10-27 12:48 ` Myklebust, Trond
2013-10-28 0:14 ` Christoph Anton Mitterer
2013-10-28 0:19 ` Myklebust, Trond
2013-10-28 0:23 ` Christoph Anton Mitterer
2013-10-28 13:25 ` James Morris
2013-10-28 15:41 ` Ric Wheeler
2013-10-26 17:12 ` Christoph Anton Mitterer
2013-10-27 19:15 ` J. Bruce Fields
2013-10-27 21:57 ` Christoph Anton Mitterer
2013-10-28 0:17 ` Myklebust, Trond
2013-10-28 0:27 ` Christoph Anton Mitterer
2013-10-28 0:44 ` Myklebust, Trond
2013-10-28 1:04 ` Christoph Anton Mitterer
2013-10-28 15:40 ` Ric Wheeler
2013-10-28 16:15 ` Christoph Anton Mitterer
2013-10-28 17:49 ` Myklebust, Trond
2013-10-28 18:00 ` Ric Wheeler
2013-10-28 18:08 ` Dr Fields James Bruce
2013-10-28 18:31 ` Ric Wheeler
2013-10-28 20:44 ` Marc Eshel
2013-10-28 20:49 ` [nfsv4] " Spencer Shepler
2013-10-28 20:55 ` Haynes, Tom
2013-10-28 21:02 ` J. Bruce Fields
2013-10-28 21:04 ` Chuck Lever
2013-10-28 21:28 ` Marc Eshel
[not found] ` <OF3A48E6D9.7BB93CB0-ON88257C12.0075527E-88257C12.0075F065@LocalDomain>
2013-10-28 22:28 ` XATTRs in NFS Marc Eshel
2013-10-28 22:41 ` Marc Eshel
[not found] ` <5272742D.7000905@redhat.com>
2013-10-31 20:54 ` Anand Avati
2013-10-31 21:36 ` [nfsv4] " Nico Williams
2013-10-28 23:02 ` Nico Williams
2013-10-28 21:28 ` [nfsv4] XATTRs in NFS? Marc Eshel
[not found] ` <526EC3F7.3090601@gmail.com>
2013-10-29 0:22 ` Fwd: " Anand Avati
2013-10-29 0:39 ` Christoph Anton Mitterer [this message]
2013-10-29 0:53 ` Myklebust, Trond
2013-10-29 1:04 ` Christoph Anton Mitterer
2013-10-29 0:49 ` Myklebust, Trond
2013-10-29 1:00 ` Ric Wheeler
2013-10-29 1:26 ` Myklebust, Trond
2013-10-29 1:24 ` Anand Avati
2013-10-29 1:52 ` Myklebust, Trond
2013-10-29 2:22 ` Anand Avati
2013-10-29 1:39 ` Christoph Anton Mitterer
2013-10-29 2:28 ` Myklebust, Trond
2013-10-29 4:27 ` Marc Eshel
2013-10-28 21:34 ` Matt W. Benjamin
2013-10-28 18:15 ` Christoph Anton Mitterer
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=1383007167.8774.52.camel@heisenberg.scientia.net \
--to=calestyo@scientia.net \
--cc=Trond.Myklebust@netapp.com \
--cc=aavati@redhat.com \
--cc=bfields@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rwheeler@redhat.com \
--cc=steved@redhat.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;
as well as URLs for NNTP newsgroup(s).