On Tue, May 01, 2012 at 06:56:06PM +0800, Liu Yuan wrote: > I guess you might misunderstand the patch. The deleting VDI operation is > very hard for a distributed cluster, which is subject to node failures. > Current async deleting makes it harder to get it right. > > before the path: > 1) inode is deleted before data object > 2) if failure happens, we don't have any means to try delete again since > inode is deleted. > > This patch set aims to > 1) delete data object before inode object > 2) when the failure happens (some data object is migrated thus > err-return), we still have the name in vdi list output with size 0, > which means last deleting is failed and we can try delete it again. > 3) if deleting success, we don't see it in VDI list output. I don't think it should sporadically fail. Especially not for the trivial testcase I posted earlier. |