[Bugs] [Bug 1369839] File locking error while brick restarting

bugzilla at redhat.com bugzilla at redhat.com
Fri Aug 26 05:20:54 UTC 2016


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

Atin Mukherjee <amukherj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |Triaged
          Component|glusterd                    |distribute



--- Comment #4 from Atin Mukherjee <amukherj at redhat.com> ---
I went through the scripts and log files. From the scripts, it looks like you
are trying a negative test scenario with every 2 secs killing the brick
processes and restarting glusterd and at the same time trying to issue flock
from the mount point. If the brick processes are going through a restart at
that time, the fops are bound to fail as client wouldn't be able to communicate
to bricks. But ideally the failures should have been transport endpoint not
connected instead of file not found. 

I am moving this BZ to distribute component for further analysis.

-- 
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