Bug 812342

Created attachment 577328 [details]
A C program that can test that the GlusterFS does not support inotify

Description of feature:

Inotify is a Linux kernel feature that monitors file systems and immediately alerts an attentive application to relevant events, such as a delete, read, write, and even an unmount operation. You can also track the origin and destination of a move, among other niceties.
Well, it would be nice to have this implemented in GlusterFS. To register directly to a system call, instead of checking the inode with a program/script.

Version-Release number of selected component (if applicable):

I leave it to your criteria, the version release number. But i think it would be awesome. Contact me if i can help in any way.

How reproducible:

I leave a c source file attached to this request. You can compile it and see that in the mounted point you choose ( you need to edit the file ) got no response from the program.

Steps to Reproduce:
1. Download de file.
2. Edit it and put the path to a mounted GlusterFS.
3. Run it.
  
Actual results:

No stdout

Expected results:

The directory/file was deleted/created/modified

Additional info:

The application creates an inotify instance with fd = inotify_init(); and adds one watch to monitor modifications, new files, and destroyed files in /path/to/mount/point, as specified by wd = inotify_add_watch(...). The read() method blocks until one or more alerts arrive. The specifics of the alert(s)—each file, each event—are sent as a stream of bytes; hence, the loop in the application casts the stream of bytes into a series of event structures.

There is a beautiful article of this, written by Ian Shields in this link http://www.ibm.com/developerworks/linux/library/l-inotify/

Cheers. And thank you, in advance.

Joaquin Diaz Treat