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

[bugzilla at redhat.com]

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

            Bug ID: 1369839
           Summary: File locking error while brick restarting
           Product: GlusterFS
           Version: 3.8.2
         Component: glusterd
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: mckornfield at gmail.com
                CC: bugs at gluster.org



Created attachment 1193658
  --> https://bugzilla.redhat.com/attachment.cgi?id=1193658&action=edit
Two scripts used to reproduce error

Description of problem:

While a brick restart is occurring (by running service glusterd restart), there
is a brief window under which file locking fails. 
We have attached two scripts that should be run simultaneously to simulate file
locking and run brick restarts to reproduce the error.

Version-Release number of selected component (if applicable):
Seen on 3.8.1 and 3.8.2

How reproducible:
Can reproduce consistently on different gluster installations

Steps to Reproduce:
1. Connect to a site running gluster
2. Run the kill-brick-process.sh script
3. Run the createAndLock.sh script while the previous script is running

Actual results:
Get a file not found error for the file generated in createAndLock.sh

Expected results:
File is locked and no error is output

Additional info:
Originally found the issue through mysql, which showed a file not found error
when attempting to lock files.
mysqld: 2016-08-08T17:26:58.383273Z 9 [ERROR] InnoDB: Unable to lock ... error:
2
mysqld: 2016-08-08T17:26:58.384050Z 9 [ERROR] InnoDB: Operating system error
number 2 in a file operation.
mysqld: 2016-08-08T17:26:58.384068Z 9 [ERROR] InnoDB: The error means the
system cannot find the path specified.
mysqld: 2016-08-08T17:26:58.384075Z 9 [ERROR] InnoDB: Cannot create file ...

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