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:
REVIEW: https://review.gluster.org/24190 (WORM-Xlator: Initial write of a file succeeds if auto-commit-period 0) posted (#1) for review on master by David Spisla
This bug is moved to https://github.com/gluster/glusterfs/issues/1020, and will be tracked there from now on. Visit GitHub issues URL for further details
REVIEW: https://review.gluster.org/24190 (WORM-Xlator: Initial write of a file succeeds if auto-commit-period 0) merged (#4) on master by Amar Tumballi