tahoe-lafs/docs/proposed
2018-05-18 13:01:10 -04:00
..
magic-folder link to inotify wikipedia page 2018-04-20 14:42:33 -04:00
accounting-overview.txt Add a link in accounting-overview.txt to ticket . 2013-07-04 12:47:28 -07:00
denver.txt docs: move files that are about future plans into docs/proposed/, to clearly separate them from descriptions of the present codebase 2008-06-02 23:07:02 -07:00
GridID.txt Minor updates to URLs. 2012-03-13 20:28:53 +00:00
http-storage-node-protocol.rst maybe we don't even want Range 2018-05-18 13:01:10 -04:00
index.rst initial pass over security section 2018-05-14 14:30:34 -04:00
leasedb.rst format docs for Sphinx 2016-03-30 01:26:47 -07:00
lossmodel.lyx Lossmodel updates 2009-07-28 15:44:30 -07:00
mutable-DSA.svg docs: move files that are about future plans into docs/proposed/, to clearly separate them from descriptions of the present codebase 2008-06-02 23:07:02 -07:00
mutable-DSA.txt Update hyperlinks between docs, and linkify some external references. refs 2010-12-11 21:14:59 -08:00
mutsemi.svg docs: proposed mutable file crypto design with ECDSA, 96-bit private keys, and semi-private keys (from http://allmydata.org/~zooko/lafs.pdf ) 2008-09-25 14:34:57 -07:00
old-accounts-introducer.txt docs/proposed: move old accounting docs out of the way 2009-03-23 18:54:57 -07:00
old-accounts-pubkey.txt docs/proposed: move old accounting docs out of the way 2009-03-23 18:54:57 -07:00
README.lossmodel LAFS now stands for "Least-Authority File Store" rather than "Least-Authority File System". refs 2017-06-06 11:20:49 +01:00

The lossmodel.lyx file is the source document for an in-progress paper
that analyzes the probability of losing files stored in a Tahoe-LAFS
file store under various scenarios.  It describes:

1.  How to estimate peer reliabilities, based on peer MTBF failure
data.

2.  How to compute file loss probabilities, based on a given set of
shares stored on peers with estimated reliabilities.  The peer
reliabilities do not have to be uniform, and the model takes into
account the file repair process.

3.  How to estimate Tahoe parameters for k (shares needed), n (shares
distributed) and A (repair interval) to achieve a file reliability
target.

4.  How to compute the estimated repair cost over time, discounted at
a fixed rate, of maintaining a file for a time period T.

Future work will also address the latter three issues in the context
of "non-aggressive" repair, where repair will only be performed if
too many shares are lost, and it will also extend the repair cost
estimation model to suggest cost functions appropriate for common
network architectures.

A PDF of the current version of the file may be downloaded from:

    http://willden.org/~shawn/lossmodel.pdf