[Bugs] [Bug 1808421] New: WORM: If autocommit-period 0 file will be WORMed with 0 Byte during initial write

bugzilla at redhat.com bugzilla at redhat.com
Fri Feb 28 13:48:41 UTC 2020


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

            Bug ID: 1808421
           Summary: WORM: If autocommit-period 0 file will be WORMed with
                    0 Byte during initial write
           Product: GlusterFS
           Version: mainline
            Status: NEW
         Component: core
          Assignee: bugs at gluster.org
          Reporter: david.spisla at iternity.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community



Description of problem:
If worm-file-level enabled and auto-commit-period 0 an initial write
of a file (e.g. $ echo test >> file1.txt) would lead to an zero byte
file because the WORM xlator immediately WORMed the file when it was
created.


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

How reproducible:
Steps to Reproduce:
1. Enable worm-file-level for a volume and set auto-commit-period to 0
2. Mount the volume e.g. FUSE, NFS or SMB
3. Write a file e.g. $ echo test >> file1.txt or copy some file to the
mountpoint

Actual results:
File will have O Byte and it is WORMed


Expected results:
The new file respective copy should be complete and it is WORMed
(one can check the comleteness with a md5 checksum of the original and new
copy)


Additional info:

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


More information about the Bugs mailing list