[tahoe-dev] [tahoe-lafs] #390: 'readonly_storage' and 'reserved_space' not honored for mutable-slot write requests

[tahoe-lafs]

#390: 'readonly_storage' and 'reserved_space' not honored for mutable-slot write
requests
------------------------------+---------------------------------------------
     Reporter:  warner        |       Owner:                             
         Type:  defect        |      Status:  new                        
     Priority:  major         |   Milestone:  eventually                 
    Component:  code-storage  |     Version:  1.0.0                      
   Resolution:                |    Keywords:  reliability mutable backend
Launchpad Bug:                |  
------------------------------+---------------------------------------------

Comment (by davidsarah):

 Replying to [comment:17 zooko]:
 > The problem is that if you run out of space in your storage server, and
 you refuse to overwrite a mutable share with a new version, then you are
 going to continue to serve the older version, which could cause
 inefficiency, confusion, and perhaps even "rollback" events.

 OTOH, you can't in general avoid these bad things by not honouring
 {{{reserved_space}}}, because they will happen anyway if the filesystem
 runs out of space. Perhaps there is a case for starting to refuse storage
 of immutable shares at a higher reserved-space threshold than for mutable
 shares, though.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/390#comment:19>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage