From: Bryan Schumaker <bjschuma@netapp.com>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: fanotify - fschange filesystem notification on nfs mounted directory
Date: Thu, 26 Jan 2012 10:16:28 -0500 [thread overview]
Message-ID: <4F216E4C.7030907@netapp.com> (raw)
In-Reply-To: <CAAfyv35wM-G0_sFbpZ-829_Lrwz7FNT8hyPeT7XnMzF64YZ6bQ@mail.gmail.com>
On Thu Jan 26 03:00:26 2012, Belisko Marek wrote:
> Hi,
>
> I'm working on fschange
> (http://stefan.buettcher.org/cs/fschange/index.html) on which fanotify
> is based also.
>
> It is reporting changes (when file or dir is created, changed, deleted
> ...) working fine over "normal filesystems".
> Our intention is to used to report changes on directory which is
> mounted over nfs. This case doesn't work at all
> (we got some events about rename only). Is there anything what should
> be setup in nfs options or this case basically
> didn't work at all? I'm only nfs user and don't understand details.
You didn't set up anything wrong, the case just doesn't work for
finding changes on the server. Files created locally should trigger
inotify events through the VFS, but tracking changes made on the server
is more difficult. Notifications are part of the NFS v4.1 protocol,
but I don't think anything has been implemented right now.
Maybe something in userland like gamin could help?
http://people.gnome.org/~veillard/gamin/
- Bryan
>
> Thanks in advance,
>
> marek
>
prev parent reply other threads:[~2012-01-26 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 8:00 fanotify - fschange filesystem notification on nfs mounted directory Belisko Marek
2012-01-26 15:16 ` Bryan Schumaker [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=4F216E4C.7030907@netapp.com \
--to=bjschuma@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=marek.belisko@gmail.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).