From: Brian Warner Date: Fri, 13 Feb 2009 23:55:34 +0000 (-0700) Subject: NEWS: mention #625 (deep-repair breaks when it tries to repair a read-only directory) X-Git-Tag: allmydata-tahoe-1.3.0~3 X-Git-Url: https://git.rkrishnan.org/pf/content/en/footer/COPYING.TGPPL.html?a=commitdiff_plain;h=309e41cffc8a6bd76c37e8f9f2ecbc2d1bcbf118;p=tahoe-lafs%2Ftahoe-lafs.git NEWS: mention #625 (deep-repair breaks when it tries to repair a read-only directory) --- diff --git a/NEWS b/NEWS index 692fdebf..d3928e2e 100644 --- a/NEWS +++ b/NEWS @@ -32,6 +32,10 @@ limitations are: delete immutable shares. If corruption is detected, the repairer will upload replacement shares to other servers, but the corrupted shares will be left in place. + * read-only directories and read-only mutable files must be repaired by + someone who holds the write-cap: the read-cap is insufficient. Moreover, + the deep-check-and-repair operation will halt with an error if it attempts + to repair one of these read-only objects. * Some forms of corruption can cause both download and repair operations to fail. A future release will fix this, since download should be tolerant of any corruption as long as there are at least 'k' valid shares, and repair