Hide Forgot
The current framework of locking using internal locks is racy and can lead to corruption and self healing not working properly. Apart from corruption, another problem can happen - self heal / flush (full file locks) can starve due to continuous I/O and never get a lock while I/O continues. So, sometimes a flush is not immediately observed when a child goes up/down. This is especially problematic since, self heal can be blocked when a child is up and I/O continues. This coupled with the race involved as mentioned above can lead to corruption. See bug 762692 for more information.
Setting it duplicate of bug 762692, since thats where all the action has been in fixing this. *** This bug has been marked as a duplicate of bug 960 ***