Description of problem: I have 2 fuse clients through which I writing into the same file. While trying to read the file from both the clients, the output is incorrect. The output on client2 sometimes comes appended with the content written from client1. Version-Release number of selected component (if applicable): 3.3.0qa19 How reproducible: Create a volume and mount 2 fuse clients. Read and write into the same file from both the clients. Steps to Reproduce: 1. echo 'abc' > /mnt/client1/file 2. echo '123' > /mnt/client2/file 3. cat /mnt/client1/file 4. cat /mnt/client2/file Actual results: abc123 abcabc123 abc123 Expected results: It should return either 'abc' or '123' Additional info: With direct-io-mode=yes option while mounting the client, this issue was not seen. Volume Name: test Type: Distribute Volume ID: 57c127eb-5eac-4868-9e50-d108601c7422 Status: Started Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: shortwing:/falcon/d1 Brick2: shortwing:/falcon/d2 Options Reconfigured: performance.quick-read: off performance.io-cache: off performance.read-ahead: off performance.write-behind: off
Also please note that both clients are on the same machine and hence sharing same vfs. Since, it seems like fuse/kernel issue, reassigning the bug to fuse.
We need to understand the issues clearly here. Either it has to goto the documentation.
Reassigning to Csaba as this seems to be an issue in the fuse kernel module.
Just tested this with 2 nfs clients and the issue was reproducible on the nfs client too.
With just a posix-fuse volume, we can reproduce the bug. The posix open flags are not in append mode. the flag value varies: 32769-32768. The data in the backend is consistent. The issue seems to be in read.
This issue exists in release-3.2.x too.
Removing target milestone as this happens in all versions.
*** This bug has been marked as a duplicate of bug 811919 ***