No error when inotify_add_watch(/an/NFS/file)
Dear Experts,
NFS doesn't work with inotify (and it looks like it can't, certainly not before NFS v4.1). However, if I give an NFS filename to inotify_add_watch(), I don't get an error.
If it indicated an error in this case then I could easily fall back to some sort of polling. Without an error, I need some other way to detect NFS (and any other non-inotify-compatible filesystems).
Any thoughts?
Phil.
(If you Cc: me in any replies I'll see them sooner.)
Quoted 11 lines · Phil Endecott
Dear Experts,
NFS doesn't work with inotify (and it looks like it can't, certainly not before NFS v4.1). However, if I give an NFS filename to
inotify_add_watch(), I don't get an error.If it indicated an error in this case then I could easily fall back to some sort of polling. Without an error, I need some other way to detect NFS (and any other non-inotify-compatible filesystems).
Any thoughts?
The one reason I can think of that you might want that behavior is if you know you only access a given piece of the filesystem from one client at a time, and you still want inotify to work in that situation. (I'm assuming inotify still notifies you of changes that are made on the same client.)
But maybe you could handle that case by allowing inotify_add_watch() in the case where the nfs filesystem was mounted with the "nolock" option, and failing it otherwise, and telling people to turn on nolock if they're sure they know what they're doing.
--b.
Quoted 5 lines · J. Bruce Fields
Quoted 4 lines · Phil Endecott
Dear Experts,
NFS doesn't work with inotify (and it looks like it can't, certainly not before NFS v4.1). However, if I give an NFS filename to
inotify_add_watch(), I don't get an error.
Quoted 7 lines
Quoted 3 lines
If it indicated an error in this case then I could easily fall back to some sort of polling. Without an error, I need some other way to detect NFS (and any other non-inotify-compatible filesystems).
Any thoughts?
The one reason I can think of that you might want that behavior is if you know you only access a given piece of the filesystem from one client at a time, and you still want inotify to work in that situation.
That's a good point.
Quoted 2 lines
(I'm assuming inotify still notifies you of changes that are made on the same client.)
A quick test suggest that it does.
Quoted 4 lines
But maybe you could handle that case by allowing
inotify_add_watch()in the case where the nfs filesystem was mounted with the "nolock" option, and failing it otherwise, and telling people to turn on nolock if they're sure they know what they're doing.
I'm not sure what your rationale for proposing that is, and I don't think it helps in my scenario; a user wants their inotify-using application to "just work", not to be told to "sudo re-mount".
I suppose that I just need some way to determine whether I will get all, some, or none of the events that I've asked for.
Phil.
Quoted 25 lines · Phil Endecott
Quoted 11 lines · J. Bruce Fields
Quoted 10 lines · Phil Endecott
Dear Experts,
NFS doesn't work with inotify (and it looks like it can't, certainly not before NFS v4.1). However, if I give an NFS filename to
inotify_add_watch(), I don't get an error.If it indicated an error in this case then I could easily fall back to some sort of polling. Without an error, I need some other way to detect NFS (and any other non-inotify-compatible filesystems).
Quoted 5 lines
Quoted 1 line
Any thoughts?
The one reason I can think of that you might want that behavior is if you know you only access a given piece of the filesystem from one client at a time, and you still want inotify to work in that situation.
That's a good point.
Quoted 2 lines
(I'm assuming inotify still notifies you of changes that are made on the same client.)
A quick test suggest that it does.
Quoted 8 lines
Quoted 4 lines
But maybe you could handle that case by allowing
inotify_add_watch()in the case where the nfs filesystem was mounted with the "nolock" option, and failing it otherwise, and telling people to turn on nolock if they're sure they know what they're doing.I'm not sure what your rationale for proposing that is, and I don't think it helps in my scenario; a user wants their inotify-using application to "just work", not to be told to "sudo re-mount".
I agree, it doesn't help you much. But for a user that's stuck with an application that just refuses to do anything if it can't use inotify, this would allow them to tell the nfs client, "it's OK to let applications on this filesystem use inotify, because nobody else writes to this filesystem."
Quoted 2 lines
I suppose that I just need some way to determine whether I will get all, some, or none of the events that I've asked for.
Right. So you'd like to know that if an inotify watch is granted, that means you really are going to get notified about everything (either because the kernel really does have the required knowledge about every change, or in the "nfs mounted with nolock case" because the user has told the kernel it doesn't have to worry about the changes it can't track).
--b.