Suppose we're writing a file through dd with booster preloaded booster. Now if we have the same volfile  as being used by booster, mounted through FUSE. As soon as the dd file writing finishes, if do an ls on the mount point, a self-heal gets triggered. This happens consistently.

The problem has been narrowed down to the replicate *feature*..(:P) of unwinding a call before the xattrs have been set to a sane value. This means that when the close syscall returns control to booster, there is no guarantee that the file has been written sanely on all replicate children. Right after the close returns, dd exits, giving no opportunity to replicate to set the xattrs in the background.

Next, after dd exits, doing an ls makes replicate realize the inconsistent xattrs and so triggers a self-heal.

PATCH: http://patches.gluster.com/patch/1469 in master (iobuf, logging: Expose existing functions as required)

PATCH: http://patches.gluster.com/patch/1470 in master (libglusterfsclient: Clean up fini and umount code paths)

PATCH: http://patches.gluster.com/patch/1471 in master (libglusterfsclient: Wait for all call pools to be destroyed)

PATCH: http://patches.gluster.com/patch/1473 in master (booster: Cleanup booster_cleanup and register for atexit)

PATCH: http://patches.gluster.com/patch/1476 in release-2.0 (iobuf, logging: Expose existing functions as required)

PATCH: http://patches.gluster.com/patch/1477 in release-2.0 (libglusterfsclient: Clean up fini and umount code paths)

PATCH: http://patches.gluster.com/patch/1478 in release-2.0 (libglusterfsclient: Wait for all call pools to be destroyed)

PATCH: http://patches.gluster.com/patch/1480 in release-2.0 (booster: Cleanup booster_cleanup and register for atexit)