From: Jeff Layton <jlayton@redhat.com>
To: Sage Weil <sweil@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
Gregory Farnum <gfarnum@redhat.com>
Subject: change attribute support in libcephfs
Date: Thu, 14 Jul 2016 10:32:11 -0400 [thread overview]
Message-ID: <1468506731.2617.9.camel@redhat.com> (raw)
Hi Sage,
Greg suggested I run this by you before we rely on it and I'm cc'ing
ceph-devel in case anyone else has thoughts.
In the ceph userland code, the client Inode structure has a "version"
field that is a uint64_t. That appears to get incremented whenever
something changes in the data or metadata for the inode. If so, then we
may just be able to expose that as the stx_version field in a
ceph_statx() call, which ganesha could then use as a NFSv4 change
attribute.
The big question mark there of course is whether that will also work
for directories. It looks like anytime we do a getattr on a directory,
the MDS will do a gather of all the dirfrags and the version field will
change if something has changed.
Is that the case? Any other caveats to taking this approach that you
can think of?
--
Jeff Layton <jlayton@redhat.com>
reply other threads:[~2016-07-14 14:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1468506731.2617.9.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gfarnum@redhat.com \
--cc=sweil@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 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.