> But maybe this is a problem in this case, where the removed object is > still sticking around. I've been hammering reintegration lately and > ... > This is a different problem, the first step of server-server resolution > grabs a global volume lock on all replicas. This lock is released > whenever resolution completes. If the server that was chosen as the > master during the resolution dies, these locks stick around. So all > ... > This must be the resolve operation that grabbed the lock. I wonder why > it didn't manage to unlock the other replica when resolution succeeded.
So perhaps something died or got stuck in the middle of server-server
resolution? I'll watch for it happening again and try to get a gdb
trace...
Thanks for looking into this.
--
Patrick Walsh
eSoft Incorporated
303.444.1600 x3350
http://www.esoft.com/
signature.asc
Description: This is a digitally signed message part
