[tahoe-lafs-trac-stream] [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-    |    Version:  1.0.0
  storage                |   Keywords:  reliability mutable backend
   Resolution:           |  availability anti-censorship
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by zooko):

 From comment:5:ticket:1568:

 For what it is worth, I increasingly think read-only storage should be
 deprecated for all backends, and people will have to learn how to use
 their operating system if they want readonliness of storage. When we
 invented the read-only storage option, I think partly we were thinking of
 users who could read our docs but didn't want to learn how to use their
 operating system to set policy. Nowadays I'm less interested in the idea
 of such users being server operators.

 Also, the fact that we've never really finished implementing read-only
 storage (to include mutables), so that there are weird failure modes that
 could hit people who rely on it is evidence that we should not spend our
 precious engineering time on things that the operating system could do for
 us and do better.

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