[tahoe-dev] Surprise shares

[Francois Deppierraz]

Hi Brian,

Brian Warner wrote:

> So setting the server to "readonly" and also freeing up enough disk space (or
> raising the quota) should mitigate this problem for now. Merely setting the
> full server to readonly (without doing something to allow small writes to
> succeed) probably won't.

Sorry, I forgot to mention that I freed up some disk space as well.

> Oh, also, in thinking about the bug some more, and assuming that the mutable
> file publish was triggered by a directory modification, what I suspect
> will/did happen is:
> 
>  * first publish fails with UCWE due to the self-inflicted "surprise shares"
>    * note however that almost all of the shares have been updated
>  * dirnode modifier notices the UCWE and tries again
>  * second publish fails in exactly the same way. Repeat 3 or 4 times
>  * eventually the dirnode modify fails, and your 'add child' or 'delete
>    child' webapi request fails
>  * the next time you read that directory, you'll see the new version
>  * subsequent publish attempts will fail in the same way, until the server is
>    changed to not emit errors

Your scenario is pretty accurate according to attached log file.

BTW, Is there any easy way to "anonimize" flog files ? Hand editing of
the resulting html file is somewhat boring.

François
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20081222/20cc919e/attachment.html>