Hello Tobias, Tobias Wilken: > /data/applications/core/image/TESTFILE - On both machines in the ro branch > On NodeA I change the file in /data/applications/core/current, so the file > is copied to /data/share/core/files. > Via glusterfs the file is also available on NodeB in /data/share/core/files. > The problem, glusterfs is mounted via fuse and as I understood fuse isn't > capable of inotify. So the aufs mount on NodeB don't get the information of > the new file on the writable branch and uses the old file from the cache or > from the ro branch.
Then how does the replication (NodeA --> NodeB) in glusterfs/fuse work? Can you always see the latest /data/share/core/files/TESTFILE on NodeB (bypassing aufs)? As long as gluseterfs works in userspace and creates the file, the inotify should work. When and how does the file become visible in NodeB? By the way, your report is good and contains enough information. J. R. Okajima ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev
