| 2 | 2 | > It looks like the mutable filenode modification code in {{{MutableFileVersion}}} reacts to an {{{UncoordinatedWriteError}}} by performing a map update, then trying the operation again. That map update will update the {{{MutableFileVersion}}}'s internal servermap, but not its internal verinfo tuple. If the {{{UncoordinatedWriteError}}} is due to a concurrent update operation that updated all or most (enough for the version to be unrecoverable, anyway) of the shares associated with the {{{MutableFileVersion}}}'s version of the mutable file, then we would see the {{{KeyError}}} reported by vikarti and others. |
