For issue 1, there are only two things that I can think of that can make different clients see listings differently: timing and the client cache. Obviously, while the data is mutating, listing it will show it changing, and listing at different times will show different subsets of the changes. Ganesha caches directory contents, so what you see depends on when it was last cached, and which up-calls have been received. However, this is all server side, and two clients listing at the same time will get the same results. Clients listing at slightly different times will get different results, and the differences won't go away until the actual data changes are completed. The other thing is the client cache. NFS clients cache metadata (and sometimes data), and to different clients will always have slightly different views of the metadata and data as those caches are saved, invalidated, and refreshed. Ganesha has no control over this aspect of the issue. For issue 2, there's some other problem here. Ganesha does not do any data caching, all read/write calls are passed straight through to the underlying FSAL. So, if data is corrupted, it's either Gluster's fault or the client's fault. Ganesha is just a pass-through for data. I've never heard of a setup like you have, with two separate synced Gluster clusters fronted by NFS. I don't know anything about Gluster's sync processes, and so I don't know how that process interacts with the UP calls that Ganesha needs to help provide consistent access to files. My guess is that there's some issue there, but I don't know. It's also possible that the sync process isn't atomic with respect to the APIs that Ganesha uses, and that this is the source of some of the issues? I'm just guessing here, however. Daniel On 5/13/21 2:23 PM, philipmjewell(a)gmail.com wrote: