[Bugs] [Bug 1793042] New: Client receives not error when triggering autocommit with WRITE FOP

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1793042

            Bug ID: 1793042
           Summary: Client receives not error when triggering autocommit
                    with WRITE FOP
           Product: GlusterFS
           Version: 5
            Status: NEW
         Component: fuse
          Assignee: bugs at gluster.org
          Reporter: david.spisla at iternity.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community



Created attachment 1653961
  --> https://bugzilla.redhat.com/attachment.cgi?id=1653961&action=edit
Logs for Gluster FUSE and SMB Client access

Description of problem:
Client receives no error when triggering autocommit with WRITE FOP. This is
reproducible via FUSE Client and also via SMB Client using glusterfs_vfs
plugin.
In my opinion this is critical because if a client application triggers
autocommit via WRITE it thinks, the WRITE was a success and deletes the file
from its cache (client-side data loss). In the backend, of course, there is no
data loss.

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

How reproducible:
Steps to Reproduce (with FUSE client):
1. Create a gluster volume and enable worm-file-level
(180s is default for autocommit period) 
2. Mount volume via Native FUSE Client
3. In the mount path do:
$ echo test >> file1.txt && sleep 185 && echo test >> file1.txt

Actual results:
There is *no* error in bash like "Permission denied" or "Read-only filesystem"
after triggering autocommit with the second WRITE FOP

Expected results:
There should be an error message.

Additional info:
If one triggers the autocommit with RENAME or TRUNCATE there is an error
message.

In the attachment there are gluster-trace-logs (client and brick) for the above
reproducible steps.

Additionally there are also smb-logs-with-trace to have an example what happens
in a smb client (mounted via mount.cifs in the bash)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.