ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2025-02-07 11:50:21 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs/frontends/webapi.txt: note that 'count-good-share-hosts' is computed incorrectly; refs #1115

Browse Source
This commit is contained in:
david-sarah 2010-09-10 17:25:48 -07:00
parent f32dddbced
commit 0091205e3c
1 changed files with 4 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/frontends/webapi.txt
View File

@ -1172,13 +1172,10 @@ POST $URL?t=check
count-shares-good: the number of good shares that were found count-shares-good: the number of good shares that were found
count-shares-needed: 'k', the number of shares required for recovery count-shares-needed: 'k', the number of shares required for recovery
count-shares-expected: 'N', the number of total shares generated count-shares-expected: 'N', the number of total shares generated
count-good-share-hosts: the number of distinct storage servers with count-good-share-hosts: this was intended to be the number of distinct
good shares. If this number is less than storage servers with good shares. It is currently
count-shares-good, then some shares are doubled (as of Tahoe-LAFS v1.8.0) computed incorrectly;
up, increasing the correlation of failures. This see ticket #1115.
indicates that one or more shares should be
moved to an otherwise unused server, if one is
available.
count-wrong-shares: for mutable files, the number of shares for count-wrong-shares: for mutable files, the number of shares for
versions other than the 'best' one (highest versions other than the 'best' one (highest
sequence number, highest roothash). These are sequence number, highest roothash). These are