[tahoe-lafs-trac-stream] [tahoe-lafs] #1793: Clarified risks of shares.happy <= shares.needed in configuration.rst

[tahoe-lafs]

#1793: Clarified risks of shares.happy <= shares.needed in configuration.rst
-------------------------------+-------------------------------
     Reporter:  Sagi           |      Owner:  marlowe
         Type:  enhancement    |     Status:  new
     Priority:  minor          |  Milestone:  undecided
    Component:  documentation  |    Version:  1.9.2
   Resolution:                 |   Keywords:  preservation,docs
Launchpad Bug:                 |
-------------------------------+-------------------------------

Comment (by davidsarah):

 So, if shares.happy <= k, whether there is any redundancy depends on the
 share distribution. It is not the case in general that for N=6, k=H=3,
 each server is guaranteed to have 2 shares initially. That's what will
 happen if everything is working correctly (all servers have free space, no
 failures during upload), but the upload ''can'' still succeed without that
 being true.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1793#comment:2>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage