Hide Forgot
Description of problem: ========================= When writes are in progress from cifs mount, if we perform any volume set operations which changes the client graph, the writes fails with "Bad file descriptor" Version-Release number of selected component (if applicable): =============================================================== glusterfs 3.4.0.30rhs built on Aug 30 2013 08:15:37 How reproducible: ==================== Often Steps to Reproduce: ===================== 1.Create a replicate volume. Start the volume. 2.Create a cifs mount. 3.From mount point execute: "for i in `seq 1 100`; do echo "Hello $i" > file.1 ; sleep 1 ; done 4. while writes on file are in progress , set "write-behind" to "off" from one of the storage node. Actual results: ============== root@darrel [Sep-05-2013-10:14:47] > for i in `seq 1 100`; do echo "Hello $i" >&5 ; sleep 1 ; done -bash: echo: write error: Bad file descriptor -bash: echo: write error: Bad file descriptor -bash: echo: write error: Bad file descriptor -bash: echo: write error: Bad file descriptor -bash: echo: write error: Bad file descriptor -bash: echo: write error: Bad file descriptor -bash: echo: write error: Bad file descriptor -bash: echo: write error: Bad file descriptor -bash: echo: write error: Bad file descriptor -bash: echo: write error: Bad file descriptor Expected results: =================== writes shouldn't file. Additional info:
I am seeing this issue with latest gluster rpm i.e. glusterfs-server-3.4.0.31rhs-1.el6rhs.x86_64. This bug will result in data loss for on going IO when we a graph change for gluster volume. Graph change includes add-brick, remove-brick commit, volume set commands.
Posted review @ https://code.engineering.redhat.com/gerrit/12573
Verified the fix on build:- ============================ glusterfs 3.4.0.32rhs built on Sep 6 2013 10:26:11 Bug is fixed. Moving bug to verified state.
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. http://rhn.redhat.com/errata/RHBA-2013-1262.html