[Bugs] [Bug 1404693] `rm` of file on mirrored glusterfs fs sometimes blocks indefinitely

[bugzilla at redhat.com]

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

Nithya Balachandran <nbalacha at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |david.vanleeuwen at gmail.com,
                   |                            |nbalacha at redhat.com
              Flags|                            |needinfo?(david.vanleeuwen@
                   |                            |gmail.com)



--- Comment #1 from Nithya Balachandran <nbalacha at redhat.com> ---
(In reply to David van Leeuwen from comment #0)
> Description of problem:
> 
> `rm` of a file on a mirrored glusterfs filesystem blocks sometimes (~ 1 in
> 1000 times).  The file still continues to exist in both copies of the
> filesystem.  A manual `rm` of the same file removes the file, but the
> original `rm` continues to block. 
> 
> 
> Version-Release number of selected component (if applicable):
> 3.5.2-2+deb8u2 (debian jessie stock release)
> 
> 
> How reproducible:
> Mmm.  Complex Kaldi training script.  The file is probably used as a
> semaphore between parallel jobs, but is only removed until the jobs have
> finished. 
> 
> 
> Steps to Reproduce:
> 1. install two nodes with large filesystems on /mnt/gluster/data
> 2. configure as mirror: `gluster volume create data replica 2 transport tcp
> host-1:/mnt/gluster/data/brick host-2:/mnt/gluster/data/brick`
> 3. mount as /data, use this as shared filesystem. 
> 
> Actual results:
> Every so often (1 in 1000 times or less) `rm file-on-glusterfs-fs` blocks,
> nothing happens, seemingly indefinitely.  I have to kill the `rm` process
> for the  calling script to continue. 
> 
> Expected results:
> `rm file-on-glusterfs-fs` always returns within a few seconds
> 
> 
> 
> Additional info:

Hi,


Please provide the following information:

1. Mount Logs for when the problem is seen
2. Did the bricks already contain files when they were used to create the
volume?
3. gluster volume info

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