Description of problem: ======================= When storage reserve limit is reached, appending data to an existing file throws EROFS error. Version-Release number of selected component (if applicable): 3.12.2-5.el7rhgs.x86_64 How reproducible: always Steps to Reproduce: =================== 1) create a x3 volume and start it. 2) Set storage.reserve volume set option to 90, gluster volume set distrepx3 storage.reserve 90 3) Create data using dd until the backend bricks reaches reserve limit. 4) Now, try appending data to the existing file. Actual results: =============== appending data to an existing file throws EROFS error cat /etc/redhat-release > 25MB_997 -bash: 25MB_997: Read-only file system Expected results: ================= It should throw appropriate error, ENOSPC.
Verified this BZ on glusterfs version 3.12.2-8.el7rhgs.x86_64. Now, when storage reserve limit is reached, appending data to an existing file is throwing ENOSPC error as expected. Moving this BZ to Verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2607