Hide Forgot
This is the case of frame loss in write-behind, where an fop gets stuck in write-behind request queue, never to be resumed again.
PATCH: http://patches.gluster.com/patch/3453 in master (performance/write-behind: explicitly enforce ordering of overlapping writes.)
latest git pull on release-3.0 does not have this issue. I think we can close this bug.
Run as part of daily sanity. So regression testcase not required.