id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,launchpad_bug 200,"writing of shares is fragile and ""tahoe stop"" is unnecessarily harsh",zooko,warner,"As per comment:ticket:181:8, the updating of share data is an incremental in-place process on disk, which means that if the node crashes during updating a share, the share will be corrupted. Also, there is not currently a way to deliberately stop (or restart) node without crashing it. I'm inclined to measure the I/O cost of more robust atomic update of shares, but I'll leave it up to Brian and assign this ticket to him.",enhancement,new,major,eventually,code-storage,0.6.1,,reliability,,