Bug 762777 (GLUSTER-1045)

locktests fails on a file if I/O is going on that file, when flush-behind option is on(which id the default). Turning flush-behind off works fine and locktests work fine.

Steps to reproduce:

Keep writing to a file in a loop (dd in this case), and parellely run locktests on that file ( 2 clients were used in this case). locktests fails saying some of the opearations are failed:



process number running test successfully :
50 process of 50 successfully ran test : WRITE ON A READ  LOCK
50 process of 50 successfully ran test : WRITE ON A WRITE LOCK
50 process of 50 successfully ran test : READ  ON A READ  LOCK
50 process of 50 successfully ran test : READ  ON A WRITE LOCK
50 process of 50 successfully ran test : SET A READ  LOCK ON A READ  LOCK
49 process of 50 successfully ran test : SET A WRITE LOCK ON A WRITE LOCK
50 process of 50 successfully ran test : SET A WRITE LOCK ON A READ  LOCK
0 process of 50 successfully ran test : SET A READ  LOCK ON A WRITE LOCK
50 process of 50 successfully ran test : READ LOCK THE WHOLE FILE BYTE BY BYTE
50 process of 50 successfully ran test : WRITE LOCK THE WHOLE FILE BYTE BY BYTE
Init


Here out of 50 processes 49 processes are successful at one point and none of the processes are successful at the other.