1 ==================================
2 User-Visible Changes in Tahoe-LAFS
3 ==================================
5 Release 1.9.0 (2011-??-??)
6 --------------------------
15 - immutable-download timeline viz (#?)
16 - drop-upload feature (experimental) #1429
18 Configuration/Behavior Changes
20 - reject old-style (discrete) config files from <v1.3 #1385
21 - measure space of storage/shares/, not storage/ #1384
22 - 'tahoe cp xyz MUTABLE' will modify the existing mutable file instead of
24 - WUI button says "unlink" instead of "del", change docs, allow 'tahoe
29 - 'tahoe put/cp' uploads didn't appear in history #1079
30 - verifier: serialize block fetches, reduce RAM footprint #1395
31 - make large immutable downloads faster (coalesce Share.loop() calls) #1268
35 - remove debian packaging #1454
36 - remove contrib/fuse #1409
37 - The unmaintained FUSE plugins were removed from the source tree. See
38 docs/frontends/FTP-and-SFTP.rst for how to use sshfs. (`#1409`_)
39 - replace foolscap[secure_connections] dep with one on pyopenssl #1383
40 - bump Twisted dependency to >=10.1
41 - bump zope.interface dep to <=3.6.2 or >=3.6.6 #1435
42 - extra-permission changes in license
43 - no longer need to patch Twisted for FTP, when using Twisted >= 10.1
47 - minor: #1355, #1366, #1388, #1389, #1391, #1297, #1342, #1404, #1392,
48 #1412, #1344, #1345, #1347, #1334, #1274, #1438, #1120, #1359, #636, #1469,
49 #1149, #1441, #1503, #1510, #1507, #1505
50 - minor SFTP fixes: #1442, #1446
51 - finish .rst-ifying all docs
52 - shuffle configuration.rst to add Frontend section
54 - IServer refactoring #1363
55 - Nodes now emit "None" for percentiles with higher implied precision
56 than the number of observations can support. Older stats gatherers
57 will throw an exception if they gather stats from a new storage
58 server and it sends a "None" for a percentile. (`#1392`_)
61 Compatibility and Dependencies
62 ''''''''''''''''''''''''''''''
64 - An incompatibility of zope.interface version 3.6.4 with Nevow has
65 been resolved. Tahoe-LAFS now requires one of the exact versions
66 v3.3.1, v3.5.3, or v3.6.1 of zope.interface. (`#1435`_)
67 - The Twisted dependency has been raised to version 10.1. This ensures
68 that we no longer require pywin32 on Windows, and that it is never
69 necessary to patch Twisted in order to use the FTP frontend.
72 .. _`#1274`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1274
73 .. _`#1392`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1392
74 .. _`#1409`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1409
75 .. _`#1435`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1435
76 .. _`#1438`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1438
79 ** Security-related Bugfix
81 - Fix flaw that would allow a person who knows a storage index of a file to
82 delete shares of that file (#1528).
83 - Remove corner cases in mutable file bounds management which could expose
84 extra lease info or old share data (from prior versions of the mutable
85 file) if someone with write authority to that mutable file exercised these
86 corner cases in a way that no actual Tahoe-LAFS client does. (Probably not
87 exploitable.) (#1528).
90 Release 1.8.3 (2011-09-13)
91 --------------------------
93 Security-related Bugfix
94 '''''''''''''''''''''''
96 - Fix flaw that would allow a person who knows a storage index of a file to
97 delete shares of that file (#1528).
98 - Remove corner cases in mutable file bounds management which could expose
99 extra lease info or old share data (from prior versions of the mutable
100 file) if someone with write authority to that mutable file exercised these
101 corner cases in a way that no actual Tahoe-LAFS client does. (Probably not
102 exploitable.) (#1528).
105 Release 1.8.2 (2011-01-30)
106 --------------------------
108 Compatibility and Dependencies
109 ''''''''''''''''''''''''''''''
111 - Tahoe is now compatible with Twisted-10.2 (released last month), as
112 well as with earlier versions. The previous Tahoe-1.8.1 release
113 failed to run against Twisted-10.2, raising an AttributeError on
114 StreamServerEndpointService (`#1286`_)
115 - Tahoe now depends upon the "mock" testing library, and the foolscap
116 dependency was raised to 0.6.1 . It no longer requires pywin32
117 (which was used only on windows). Future developers should note that
118 reactor.spawnProcess and derivatives may no longer be used inside
124 - the default reserved_space value for new storage nodes is 1 GB
126 - documentation is now in reStructuredText (.rst) format
127 - "tahoe cp" should now handle non-ASCII filenames
128 - the unmaintained Mac/Windows GUI applications have been removed
130 - tahoe processes should appear in top and ps as "tahoe", not
131 "python", on some unix platforms. (`#174`_)
132 - "tahoe debug trial" can be used to run the test suite (`#1296`_)
133 - the SFTP frontend now reports unknown sizes as "0" instead of "?",
134 to improve compatibility with clients like FileZilla (`#1337`_)
135 - "tahoe --version" should now report correct values in situations
136 where 1.8.1 might have been wrong (`#1287`_)
138 .. _`#174`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/174
139 .. _`#1208`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1208
140 .. _`#1282`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1282
141 .. _`#1286`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1286
142 .. _`#1287`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1287
143 .. _`#1296`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1296
144 .. _`#1337`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1337
147 Release 1.8.1 (2010-10-28)
148 --------------------------
150 Bugfixes and Improvements
151 '''''''''''''''''''''''''
153 - Allow the repairer to improve the health of a file by uploading some
154 shares, even if it cannot achieve the configured happiness
155 threshold. This fixes a regression introduced between v1.7.1 and
157 - Fix a memory leak in the ResponseCache which is used during mutable
158 file/directory operations. (`#1045`_)
159 - Fix a regression and add a performance improvement in the
160 downloader. This issue caused repair to fail in some special
162 - Fix a bug that caused 'tahoe cp' to fail for a grid-to-grid copy
163 involving a non-ASCII filename. (`#1224`_)
164 - Fix a rarely-encountered bug involving printing large strings to the
165 console on Windows. (`#1232`_)
166 - Perform ~ expansion in the --exclude-from filename argument to
167 'tahoe backup'. (`#1241`_)
168 - The CLI's 'tahoe mv' and 'tahoe ln' commands previously would try to
169 use an HTTP proxy if the HTTP_PROXY environment variable was set.
170 These now always connect directly to the WAPI, thus avoiding giving
171 caps to the HTTP proxy (and also avoiding failures in the case that
172 the proxy is failing or requires authentication). (`#1253`_)
173 - The CLI now correctly reports failure in the case that 'tahoe mv'
174 fails to unlink the file from its old location. (`#1255`_)
175 - 'tahoe start' now gives a more positive indication that the node has
177 - The arguments seen by 'ps' or other tools for node processes are now
178 more useful (in particular, they include the path of the 'tahoe'
179 script, rather than an obscure tool named 'twistd'). (`#174`_)
184 - The tahoe start/stop/restart and node creation commands no longer
185 accept the -m or --multiple option, for consistency between
186 platforms. (`#1262`_)
191 - We now host binary packages so that users on certain operating
192 systems can install without having a compiler.
193 <http://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html>
194 - Use a newer version of a dependency if needed, even if an older
195 version is installed. This would previously cause a VersionConflict
197 - Use a precompiled binary of a dependency if one with a sufficiently
198 high version number is available, instead of attempting to compile
199 the dependency from source, even if the source version has a higher
200 version number. (`#1233`_)
205 - All current documentation in .txt format has been converted to .rst
207 - Added docs/backdoors.rst declaring that we won't add backdoors to
208 Tahoe-LAFS, or add anything to facilitate government access to data.
211 .. _`#71`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/71
212 .. _`#174`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/174
213 .. _`#1212`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1212
214 .. _`#1045`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1045
215 .. _`#1190`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1190
216 .. _`#1216`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1216
217 .. _`#1223`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1223
218 .. _`#1224`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1224
219 .. _`#1225`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1225
220 .. _`#1232`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1232
221 .. _`#1233`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1233
222 .. _`#1241`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1241
223 .. _`#1253`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1253
224 .. _`#1255`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1255
225 .. _`#1262`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1262
228 Release 1.8.0 (2010-09-23)
229 --------------------------
234 - A completely new downloader which improves performance and
235 robustness of immutable-file downloads. It uses the fastest K
236 servers to download the data in K-way parallel. It automatically
237 fails over to alternate servers if servers fail in mid-download. It
238 allows seeking to arbitrary locations in the file (the previous
239 downloader which would only read the entire file sequentially from
240 beginning to end). It minimizes unnecessary round trips and
241 unnecessary bytes transferred to improve performance. It sends
242 requests to fewer servers to reduce the load on servers (the
243 previous one would send a small request to every server for every
244 download) (`#287`_, `#288`_, `#448`_, `#798`_, `#800`_, `#990`_,
246 - Non-ASCII command-line arguments and non-ASCII outputs now work on
247 Windows. In addition, the command-line tool now works on 64-bit
250 Bugfixes and Improvements
251 '''''''''''''''''''''''''
253 - Document and clean up the command-line options for specifying the
254 node's base directory. (`#188`_, `#706`_, `#715`_, `#772`_,
256 - The default node directory for Windows is ".tahoe" in the user's
257 home directory, the same as on other platforms. (`#890`_)
258 - Fix a case in which full cap URIs could be logged. (`#685`_,
260 - Fix bug in WUI in Python 2.5 when the system clock is set back to
261 1969. Now you can use Tahoe-LAFS with Python 2.5 and set your system
262 clock to 1969 and still use the WUI. (`#1055`_)
263 - Many improvements in code organization, tests, logging,
264 documentation, and packaging. (`#983`_, `#1074`_, `#1108`_,
265 `#1127`_, `#1129`_, `#1131`_, `#1166`_, `#1175`_)
270 - on x86 and x86-64 platforms, pycryptopp >= 0.5.20
271 - pycrypto 2.2 is excluded due to a bug
273 .. _`#188`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/188
274 .. _`#287`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/287
275 .. _`#288`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/288
276 .. _`#448`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/448
277 .. _`#685`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/685
278 .. _`#706`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/706
279 .. _`#715`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/715
280 .. _`#772`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/772
281 .. _`#798`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/798
282 .. _`#800`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/800
283 .. _`#890`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/890
284 .. _`#983`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/983
285 .. _`#990`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/990
286 .. _`#1055`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1055
287 .. _`#1074`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1074
288 .. _`#1108`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1108
289 .. _`#1155`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1155
290 .. _`#1170`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1170
291 .. _`#1191`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1191
292 .. _`#1127`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1127
293 .. _`#1129`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1129
294 .. _`#1131`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1131
295 .. _`#1166`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1166
296 .. _`#1175`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1175
298 Release 1.7.1 (2010-07-18)
299 --------------------------
301 Bugfixes and Improvements
302 '''''''''''''''''''''''''
304 - Fix bug in which uploader could fail with AssertionFailure or report
305 that it had achieved servers-of-happiness when it hadn't. (`#1118`_)
306 - Fix bug in which servers could get into a state where they would
307 refuse to accept shares of a certain file (`#1117`_)
308 - Add init scripts for managing the gateway server on Debian/Ubuntu
310 - Fix bug where server version number was always 0 on the welcome page
312 - Add new command-line command "tahoe unlink" as a synonym for "tahoe
314 - The FTP frontend now encrypts its temporary files, protecting their
315 contents from an attacker who is able to read the disk. (`#1083`_)
316 - Fix IP address detection on FreeBSD 7, 8, and 9 (`#1098`_)
317 - Fix minor layout issue in the Web User Interface with Internet
319 - Fix rarely-encountered incompatibility between Twisted logging
320 utility and the new unicode support added in v1.7.0 (`#1099`_)
321 - Forward-compatibility improvements for non-ASCII caps (`#1051`_)
326 - Simplify and tidy-up directories, unicode support, test code
327 (`#923`_, `#967`_, `#1072`_)
329 .. _`#776`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/776
330 .. _`#923`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/923
331 .. _`#961`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/961
332 .. _`#967`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/967
333 .. _`#1051`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1051
334 .. _`#1067`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1067
335 .. _`#1072`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1072
336 .. _`#1083`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1083
337 .. _`#1097`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1097
338 .. _`#1098`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1098
339 .. _`#1099`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1099
340 .. _`#1117`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1117
341 .. _`#1118`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1118
344 Release 1.7.0 (2010-06-18)
345 --------------------------
350 - SFTP support (`#1037`_)
351 Your Tahoe-LAFS gateway now acts like a full-fledged SFTP server. It
352 has been tested with sshfs to provide a virtual filesystem in Linux.
353 Many users have asked for this feature. We hope that it serves them
354 well! See the `FTP-and-SFTP.rst`_ document to get
356 - support for non-ASCII character encodings (`#534`_)
357 Tahoe-LAFS now correctly handles filenames containing non-ASCII
358 characters on all supported platforms:
360 - when reading files in from the local filesystem (such as when you
361 run "tahoe backup" to back up your local files to a Tahoe-LAFS
363 - when writing files out to the local filesystem (such as when you
364 run "tahoe cp -r" to recursively copy files out of a Tahoe-LAFS
366 - when displaying filenames to the terminal (such as when you run
367 "tahoe ls"), subject to limitations of the terminal and locale;
368 - when parsing command-line arguments, except on Windows.
370 - Servers of Happiness (`#778`_)
371 Tahoe-LAFS now measures during immutable file upload to see how well
372 distributed it is across multiple servers. It aborts the upload if
373 the pieces of the file are not sufficiently well-distributed.
374 This behavior is controlled by a configuration parameter called
375 "servers of happiness". With the default settings for its erasure
376 coding, Tahoe-LAFS generates 10 shares for each file, such that any
377 3 of those shares are sufficient to recover the file. The default
378 value of "servers of happiness" is 7, which means that Tahoe-LAFS
379 will guarantee that there are at least 7 servers holding some of the
380 shares, such that any 3 of those servers can completely recover your
381 file. The new upload code also distributes the shares better than the
382 previous version in some cases and takes better advantage of
383 pre-existing shares (when a file has already been previously
384 uploaded). See the `architecture.rst`_ document [3] for details.
386 Bugfixes and Improvements
387 '''''''''''''''''''''''''
389 - Premature abort of upload if some shares were already present and
390 some servers fail. (`#608`_)
391 - python ./setup.py install -- can't create or remove files in install
393 - Network failure => internal TypeError. (`#902`_)
394 - Install of Tahoe on CentOS 5.4. (`#933`_)
395 - CLI option --node-url now supports https url. (`#1028`_)
396 - HTML/CSS template files were not correctly installed under
398 - MetadataSetter does not enforce restriction on setting "tahoe"
400 - ImportError: No module named
401 setuptools_darcs.setuptools_darcs. (`#1054`_)
402 - Renamed Title in xhtml files. (`#1062`_)
403 - Increase Python version dependency to 2.4.4, to avoid a critical
404 CPython security bug. (`#1066`_)
405 - Typo correction for the munin plugin tahoe_storagespace. (`#968`_)
406 - Fix warnings found by pylint. (`#973`_)
407 - Changing format of some documentation files. (`#1027`_)
408 - the misc/ directory was tied up. (`#1068`_)
409 - The 'ctime' and 'mtime' metadata fields are no longer written except
410 by "tahoe backup". (`#924`_)
411 - Unicode filenames in Tahoe-LAFS directories are normalized so that
412 names that differ only in how accents are encoded are treated as the
414 - Various small improvements to documentation. (`#937`_, `#911`_,
420 - The 'tahoe debug consolidate' subcommand (for converting old
421 allmydata Windows client backups to a newer format) has been
427 - the Python version dependency is raised to 2.4.4 in some cases
428 (2.4.3 for Redhat-based Linux distributions, 2.4.2 for UCS-2 builds)
432 - mock (only required by unit tests)
434 .. _`#534`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/534
435 .. _`#608`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/608
436 .. _`#778`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/778
437 .. _`#803`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/803
438 .. _`#902`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/902
439 .. _`#911`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/911
440 .. _`#924`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/924
441 .. _`#937`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/937
442 .. _`#933`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/933
443 .. _`#968`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/968
444 .. _`#973`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/973
445 .. _`#1024`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1024
446 .. _`#1027`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1027
447 .. _`#1028`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1028
448 .. _`#1033`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1033
449 .. _`#1034`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1034
450 .. _`#1037`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1037
451 .. _`#1054`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1054
452 .. _`#1062`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1062
453 .. _`#1066`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1066
454 .. _`#1068`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1068
455 .. _`#1076`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1076
456 .. _`#1082`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1082
457 .. _architecture.rst: docs/architecture.rst
458 .. _FTP-and-SFTP.rst: docs/frontends/FTP-and-SFTP.rst
460 Release 1.6.1 (2010-02-27)
461 --------------------------
466 - Correct handling of Small Immutable Directories
468 Immutable directories can now be deep-checked and listed in the web
469 UI in all cases. (In v1.6.0, some operations, such as deep-check, on
470 a directory graph that included very small immutable directories,
471 would result in an exception causing the whole operation to abort.)
474 Usability Improvements
475 ''''''''''''''''''''''
477 - Improved user interface messages and error reporting. (`#681`_,
479 - The timeouts for operation handles have been greatly increased, so
480 that you can view the results of an operation up to 4 days after it
481 has completed. After viewing them for the first time, the results
482 are retained for a further day. (`#577`_)
484 Release 1.6.0 (2010-02-01)
485 --------------------------
490 - Immutable Directories
492 Tahoe-LAFS can now create and handle immutable
493 directories. (`#607`_, `#833`_, `#931`_) These are read just like
494 normal directories, but are "deep-immutable", meaning that all their
495 children (and everything reachable from those children) must be
496 immutable objects (i.e. immutable or literal files, and other
497 immutable directories).
499 These directories must be created in a single webapi call that
500 provides all of the children at once. (Since they cannot be changed
501 after creation, the usual create/add/add sequence cannot be used.)
502 They have URIs that start with "URI:DIR2-CHK:" or "URI:DIR2-LIT:",
503 and are described on the human-facing web interface (aka the "WUI")
504 with a "DIR-IMM" abbreviation (as opposed to "DIR" for the usual
505 read-write directories and "DIR-RO" for read-only directories).
507 Tahoe-LAFS releases before 1.6.0 cannot read the contents of an
508 immutable directory. 1.5.0 will tolerate their presence in a
509 directory listing (and display it as "unknown"). 1.4.1 and earlier
510 cannot tolerate them: a DIR-IMM child in any directory will prevent
511 the listing of that directory.
513 Immutable directories are repairable, just like normal immutable
516 The webapi "POST t=mkdir-immutable" call is used to create immutable
517 directories. See `webapi.rst`_ for details.
519 - "tahoe backup" now creates immutable directories, backupdb has
522 The "tahoe backup" command has been enhanced to create immutable
523 directories (in previous releases, it created read-only mutable
524 directories) (`#828`_). This is significantly faster, since it does
525 not need to create an RSA keypair for each new directory. Also
526 "DIR-IMM" immutable directories are repairable, unlike "DIR-RO"
527 read-only mutable directories at present. (A future Tahoe-LAFS
528 release should also be able to repair DIR-RO.)
530 In addition, the backupdb (used by "tahoe backup" to remember what
531 it has already copied) has been enhanced to store information about
532 existing immutable directories. This allows it to re-use directories
533 that have moved but still contain identical contents, or that have
534 been deleted and later replaced. (The 1.5.0 "tahoe backup" command
535 could only re-use directories that were in the same place as they
536 were in the immediately previous backup.) With this change, the
537 backup process no longer needs to read the previous snapshot out of
538 the Tahoe-LAFS grid, reducing the network load
539 considerably. (`#606`_)
541 A "null backup" (in which nothing has changed since the previous
542 backup) will require only two Tahoe-side operations: one to add an
543 Archives/$TIMESTAMP entry, and a second to update the Latest/
544 link. On the local disk side, it will readdir() all your local
545 directories and stat() all your local files.
547 If you've been using "tahoe backup" for a while, you will notice
548 that your first use of it after upgrading to 1.6.0 may take a long
549 time: it must create proper immutable versions of all the old
550 read-only mutable directories. This process won't take as long as
551 the initial backup (where all the file contents had to be uploaded
552 too): it will require time proportional to the number and size of
553 your directories. After this initial pass, all subsequent passes
554 should take a tiny fraction of the time.
556 As noted above, Tahoe-LAFS versions earlier than 1.5.0 cannot list a
557 directory containing an immutable subdirectory. Tahoe-LAFS versions
558 earlier than 1.6.0 cannot read the contents of an immutable
561 The "tahoe backup" command has been improved to skip over unreadable
562 objects (like device files, named pipes, and files with permissions
563 that prevent the command from reading their contents), instead of
564 throwing an exception and terminating the backup process. It also
565 skips over symlinks, because these cannot be represented faithfully
566 in the Tahoe-side filesystem. A warning message will be emitted each
567 time something is skipped. (`#729`_, `#850`_, `#641`_)
569 - "create-node" command added, "create-client" now implies
572 The basic idea behind Tahoe-LAFS's client+server and client-only
573 processes is that you are creating a general-purpose Tahoe-LAFS
574 "node" process, which has several components that can be
575 activated. Storage service is one of these optional components, as
576 is the Helper, FTP server, and SFTP server. Web gateway
577 functionality is nominally on this list, but it is always active; a
578 future release will make it optional. There are three special
579 purpose servers that can't currently be run as a component in a
580 node: introducer, key-generator, and stats-gatherer.
582 So now "tahoe create-node" will create a Tahoe-LAFS node process,
583 and after creation you can edit its tahoe.cfg to enable or disable
584 the desired services. It is a more general-purpose replacement for
585 "tahoe create-client". The default configuration has storage
586 service enabled. For convenience, the "--no-storage" argument makes
587 a tahoe.cfg file that disables storage service. (`#760`_)
589 "tahoe create-client" has been changed to create a Tahoe-LAFS node
590 without a storage service. It is equivalent to "tahoe create-node
591 --no-storage". This helps to reduce the confusion surrounding the
592 use of a command with "client" in its name to create a storage
593 *server*. Use "tahoe create-client" to create a purely client-side
594 node. If you want to offer storage to the grid, use "tahoe
595 create-node" instead.
597 In the future, other services will be added to the node, and they
598 will be controlled through options in tahoe.cfg . The most important
599 of these services may get additional --enable-XYZ or --disable-XYZ
600 arguments to "tahoe create-node".
602 - Performance Improvements
604 Download of immutable files begins as soon as the downloader has
605 located the K necessary shares (`#928`_, `#287`_). In both the
606 previous and current releases, a downloader will first issue queries
607 to all storage servers on the grid to locate shares before it begins
608 downloading the shares. In previous releases of Tahoe-LAFS, download
609 would not begin until all storage servers on the grid had replied to
610 the query, at which point K shares would be chosen for download from
611 among the shares that were located. In this release, download begins
612 as soon as any K shares are located. This means that downloads start
613 sooner, which is particularly important if there is a server on the
614 grid that is extremely slow or even hung in such a way that it will
615 never respond. In previous releases such a server would have a
616 negative impact on all downloads from that grid. In this release,
617 such a server will have no impact on downloads, as long as K shares
618 can be found on other, quicker, servers. This also means that
619 downloads now use the "best-alacrity" servers that they talk to, as
620 measured by how quickly the servers reply to the initial query. This
621 might cause downloads to go faster, especially on grids with
622 heterogeneous servers or geographical dispersion.
627 - The webapi acquired a new "t=mkdir-with-children" command, to create
628 and populate a directory in a single call. This is significantly
629 faster than using separate "t=mkdir" and "t=set-children" operations
630 (it uses one gateway-to-grid roundtrip, instead of three or
633 - The t=set-children (note the hyphen) operation is now documented in
634 webapi.rst, and is the new preferred spelling of the
635 old t=set_children (with an underscore). The underscore version
636 remains for backwards compatibility. (`#381`_, `#927`_)
638 - The tracebacks produced by errors in CLI tools should now be in
639 plain text, instead of HTML (which is unreadable outside of a
642 - The [storage]reserved_space configuration knob (which causes the
643 storage server to refuse shares when available disk space drops
644 below a threshold) should work on Windows now, not just
647 - "tahoe cp" should now exit with status "1" if it cannot figure out a
648 suitable target filename, such as when you copy from a bare
651 - "tahoe get" no longer creates a zero-length file upon
654 - "tahoe ls" can now list single files. (`#457`_)
656 - "tahoe deep-check --repair" should tolerate repair failures now,
657 instead of halting traversal. (`#874`_, `#786`_)
659 - "tahoe create-alias" no longer corrupts the aliases file if it had
660 previously been edited to have no trailing newline. (`#741`_)
662 - Many small packaging improvements were made to facilitate the
663 "tahoe-lafs" package being included in Ubuntu. Several mac/win32
664 binary libraries were removed, some figleaf code-coverage files were
665 removed, a bundled copy of darcsver-1.2.1 was removed, and
666 additional licensing text was added.
668 - Several DeprecationWarnings for python2.6 were silenced. (`#859`_)
670 - The checker --add-lease option would sometimes fail for shares
671 stored on old (Tahoe v1.2.0) servers. (`#875`_)
673 - The documentation for installing on Windows (docs/quickstart.rst)
674 has been improved. (`#773`_)
676 For other changes not mentioned here, see
677 <http://tahoe-lafs.org/trac/tahoe/query?milestone=1.6.0&keywords=!~news-done>.
678 To include the tickets mentioned above, go to
679 <http://tahoe-lafs.org/trac/tahoe/query?milestone=1.6.0>.
681 .. _`#121`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/121
682 .. _`#287`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/287
683 .. _`#381`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/381
684 .. _`#457`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/457
685 .. _`#533`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/533
686 .. _`#577`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/577
687 .. _`#606`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/606
688 .. _`#607`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/607
689 .. _`#637`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/637
690 .. _`#641`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/641
691 .. _`#646`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/646
692 .. _`#681`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/681
693 .. _`#729`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/729
694 .. _`#741`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/741
695 .. _`#760`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/760
696 .. _`#761`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/761
697 .. _`#768`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/768
698 .. _`#773`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/773
699 .. _`#786`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/786
700 .. _`#828`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/828
701 .. _`#833`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/833
702 .. _`#859`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/859
703 .. _`#874`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/874
704 .. _`#875`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/875
705 .. _`#931`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/931
706 .. _`#837`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/837
707 .. _`#850`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/850
708 .. _`#927`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/927
709 .. _`#928`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/928
710 .. _`#939`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/939
711 .. _`#948`: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/948
712 .. _webapi.rst: docs/frontends/webapi.rst
714 Release 1.5.0 (2009-08-01)
715 --------------------------
720 - Uploads of immutable files now use pipelined writes, improving
721 upload speed slightly (10%) over high-latency connections. (`#392`_)
723 - Processing large directories has been sped up, by removing a O(N^2)
724 algorithm from the dirnode decoding path and retaining unmodified
725 encrypted entries. (`#750`_, `#752`_)
727 - The human-facing web interface (aka the "WUI") received a
728 significant CSS makeover by Kevin Reid, making it much prettier and
729 easier to read. The WUI "check" and "deep-check" forms now include a
730 "Renew Lease" checkbox, mirroring the CLI --add-lease option, so
731 leases can be added or renewed from the web interface.
733 - The CLI "tahoe mv" command now refuses to overwrite
734 directories. (`#705`_)
736 - The CLI "tahoe webopen" command, when run without arguments, will
737 now bring up the "Welcome Page" (node status and mkdir/upload
740 - The 3.5MB limit on mutable files was removed, so it should be
741 possible to upload arbitrarily-sized mutable files. Note, however,
742 that the data format and algorithm remains the same, so using
743 mutable files still requires bandwidth, computation, and RAM in
744 proportion to the size of the mutable file. (`#694`_)
746 - This version of Tahoe-LAFS will tolerate directory entries that
747 contain filecap formats which it does not recognize: files and
748 directories from the future. This should improve the user
749 experience (for 1.5.0 users) when we add new cap formats in the
750 future. Previous versions would fail badly, preventing the user from
751 seeing or editing anything else in those directories. These
752 unrecognized objects can be renamed and deleted, but obviously not
753 read or written. Also they cannot generally be copied. (`#683`_)
758 - deep-check-and-repair now tolerates read-only directories, such as
759 the ones produced by the "tahoe backup" CLI command. Read-only
760 directories and mutable files are checked, but not
761 repaired. Previous versions threw an exception when attempting the
762 repair and failed to process the remaining contents. We cannot yet
763 repair these read-only objects, but at least this version allows the
764 rest of the check+repair to proceed. (`#625`_)
766 - A bug in 1.4.1 which caused a server to be listed multiple times
767 (and frequently broke all connections to that server) was
770 - The plaintext-hashing code was removed from the Helper interface,
771 removing the Helper's ability to mount a
772 partial-information-guessing attack. (`#722`_)
774 Platform/packaging changes
775 ''''''''''''''''''''''''''
777 - Tahoe-LAFS now runs on NetBSD, OpenBSD, ArchLinux, and NixOS, and on
778 an embedded system based on an ARM CPU running at 266 MHz.
780 - Unit test timeouts have been raised to allow the tests to complete
781 on extremely slow platforms like embedded ARM-based NAS boxes, which
782 may take several hours to run the test suite. An ARM-specific
783 data-corrupting bug in an older version of Crypto++ (5.5.2) was
784 identified: ARM-users are encouraged to use recent
785 Crypto++/pycryptopp which avoids this problem.
787 - Tahoe-LAFS now requires a SQLite library, either the sqlite3 that
788 comes built-in with python2.5/2.6, or the add-on pysqlite2 if you're
789 using python2.4. In the previous release, this was only needed for
790 the "tahoe backup" command: now it is mandatory.
792 - Several minor documentation updates were made.
794 - To help get Tahoe-LAFS into Linux distributions like Fedora and
795 Debian, packaging improvements are being made in both Tahoe-LAFS and
796 related libraries like pycryptopp and zfec.
798 - The Crypto++ library included in the pycryptopp package has been
799 upgraded to version 5.6.0 of Crypto++, which includes a more
800 efficient implementation of SHA-256 in assembly for x86 or amd64
807 - no python-2.4.0 or 2.4.1 (2.4.2 is good) (they contained a bug in base64.b32decode)
808 - avoid python-2.6 on windows with mingw: compiler issues
809 - python2.4 requires pysqlite2 (2.5,2.6 does not)
813 .. _#392: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/392
814 .. _#625: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/625
815 .. _#653: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/653
816 .. _#683: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/683
817 .. _#694: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/694
818 .. _#705: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/705
819 .. _#722: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/722
820 .. _#750: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/750
821 .. _#752: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/752
823 Release 1.4.1 (2009-04-13)
824 --------------------------
829 - The big feature for this release is the implementation of garbage
830 collection, allowing Tahoe storage servers to delete shares for old
831 deleted files. When enabled, this uses a "mark and sweep" process:
832 clients are responsible for updating the leases on their shares
833 (generally by running "tahoe deep-check --add-lease"), and servers
834 are allowed to delete any share which does not have an up-to-date
835 lease. The process is described in detail in
836 `garbage-collection.rst`_.
838 The server must be configured to enable garbage-collection, by
839 adding directives to the [storage] section that define an age limit
840 for shares. The default configuration will not delete any shares.
842 Both servers and clients should be upgraded to this release to make
843 the garbage-collection as pleasant as possible. 1.2.0 servers have
844 code to perform the update-lease operation but it suffers from a
845 fatal bug, while 1.3.0 servers have update-lease but will return an
846 exception for unknown storage indices, causing clients to emit an
847 Incident for each exception, slowing the add-lease process down to a
848 crawl. 1.1.0 servers did not have the add-lease operation at all.
850 Security/Usability Problems Fixed
851 '''''''''''''''''''''''''''''''''
853 - A super-linear algorithm in the Merkle Tree code was fixed, which
854 previously caused e.g. download of a 10GB file to take several hours
855 before the first byte of plaintext could be produced. The new
856 "alacrity" is about 2 minutes. A future release should reduce this
857 to a few seconds by fixing ticket `#442`_.
859 - The previous version permitted a small timing attack (due to our use
860 of strcmp) against the write-enabler and lease-renewal/cancel
861 secrets. An attacker who could measure response-time variations of
862 approximatly 3ns against a very noisy background time of about 15ms
863 might be able to guess these secrets. We do not believe this attack
864 was actually feasible. This release closes the attack by first
865 hashing the two strings to be compared with a random secret.
870 - In most cases, HTML tracebacks will only be sent if an "Accept:
871 text/html" header was provided with the HTTP request. This will
872 generally cause browsers to get an HTMLized traceback but send
873 regular text/plain tracebacks to non-browsers (like the CLI
874 clients). More errors have been mapped to useful HTTP error codes.
876 - The streaming webapi operations (deep-check and manifest) now have a
877 way to indicate errors (an output line that starts with "ERROR"
878 instead of being legal JSON). See `webapi.rst`_ for
881 - The storage server now has its own status page (at /storage), linked
882 from the Welcome page. This page shows progress and results of the
883 two new share-crawlers: one which merely counts shares (to give an
884 estimate of how many files/directories are being stored in the
885 grid), the other examines leases and reports how much space would be
886 freed if GC were enabled. The page also shows how much disk space is
887 present, used, reserved, and available for the Tahoe server, and
888 whether the server is currently running in "read-write" mode or
891 - When a directory node cannot be read (perhaps because of insufficent
892 shares), a minimal webapi page is created so that the "more-info"
893 links (including a Check/Repair operation) will still be accessible.
895 - A new "reliability" page was added, with the beginnings of work on a
896 statistical loss model. You can tell this page how many servers you
897 are using and their independent failure probabilities, and it will
898 tell you the likelihood that an arbitrary file will survive each
899 repair period. The "numpy" package must be installed to access this
900 page. A partial paper, written by Shawn Willden, has been added to
901 docs/proposed/lossmodel.lyx .
906 - "tahoe check" and "tahoe deep-check" now accept an "--add-lease"
907 argument, to update a lease on all shares. This is the "mark" side
908 of garbage collection.
910 - In many cases, CLI error messages have been improved: the ugly
911 HTMLized traceback has been replaced by a normal python traceback.
913 - "tahoe deep-check" and "tahoe manifest" now have better error
914 reporting. "tahoe cp" is now non-verbose by default.
916 - "tahoe backup" now accepts several "--exclude" arguments, to ignore
917 certain files (like editor temporary files and version-control
918 metadata) during backup.
920 - On windows, the CLI now accepts local paths like "c:\dir\file.txt",
921 which previously was interpreted as a Tahoe path using a "c:" alias.
923 - The "tahoe restart" command now uses "--force" by default (meaning
924 it will start a node even if it didn't look like there was one
927 - The "tahoe debug consolidate" command was added. This takes a series
928 of independent timestamped snapshot directories (such as those
929 created by the allmydata.com windows backup program, or a series of
930 "tahoe cp -r" commands) and creates new snapshots that used shared
931 read-only directories whenever possible (like the output of "tahoe
932 backup"). In the most common case (when the snapshots are fairly
933 similar), the result will use significantly fewer directories than
934 the original, allowing "deep-check" and similar tools to run much
935 faster. In some cases, the speedup can be an order of magnitude or
936 more. This tool is still somewhat experimental, and only needs to
937 be run on large backups produced by something other than "tahoe
938 backup", so it was placed under the "debug" category.
940 - "tahoe cp -r --caps-only tahoe:dir localdir" is a diagnostic tool
941 which, instead of copying the full contents of files into the local
942 directory, merely copies their filecaps. This can be used to verify
943 the results of a "consolidation" operation.
948 - The codebase no longer rauses RuntimeError as a kind of
949 assert(). Specific exception classes were created for each previous
950 instance of RuntimeError.
952 -Many unit tests were changed to use a non-network test harness,
953 speeding them up considerably.
955 - Deep-traversal operations (manifest and deep-check) now walk
956 individual directories in alphabetical order. Occasional turn breaks
957 are inserted to prevent a stack overflow when traversing directories
958 with hundreds of entries.
960 - The experimental SFTP server had its path-handling logic changed
961 slightly, to accomodate more SFTP clients, although there are still
964 .. _#442: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/442
965 .. _#645: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/645
966 .. _garbage-collection.rst: docs/garbage-collection.rst
968 Release 1.3.0 (2009-02-13)
969 --------------------------
971 Checker/Verifier/Repairer
972 '''''''''''''''''''''''''
974 - The primary focus of this release has been writing a checker /
975 verifier / repairer for files and directories. "Checking" is the
976 act of asking storage servers whether they have a share for the
977 given file or directory: if there are not enough shares available,
978 the file or directory will be unrecoverable. "Verifying" is the act
979 of downloading and cryptographically asserting that the server's
980 share is undamaged: it requires more work (bandwidth and CPU) than
981 checking, but can catch problems that simple checking
982 cannot. "Repair" is the act of replacing missing or damaged shares
985 - This release includes a full checker, a partial verifier, and a
986 partial repairer. The repairer is able to handle missing shares: new
987 shares are generated and uploaded to make up for the missing
988 ones. This is currently the best application of the repairer: to
989 replace shares that were lost because of server departure or
990 permanent drive failure.
992 - The repairer in this release is somewhat able to handle corrupted
993 shares. The limitations are:
995 - Immutable verifier is incomplete: not all shares are used, and not
996 all fields of those shares are verified. Therefore the immutable
997 verifier has only a moderate chance of detecting corrupted shares.
998 - The mutable verifier is mostly complete: all shares are examined,
999 and most fields of the shares are validated.
1000 - The storage server protocol offers no way for the repairer to
1001 replace or delete immutable shares. If corruption is detected, the
1002 repairer will upload replacement shares to other servers, but the
1003 corrupted shares will be left in place.
1004 - read-only directories and read-only mutable files must be repaired
1005 by someone who holds the write-cap: the read-cap is
1006 insufficient. Moreover, the deep-check-and-repair operation will
1007 halt with an error if it attempts to repair one of these read-only
1009 - Some forms of corruption can cause both download and repair
1010 operations to fail. A future release will fix this, since download
1011 should be tolerant of any corruption as long as there are at least
1012 'k' valid shares, and repair should be able to fix any file that is
1015 - If the downloader, verifier, or repairer detects share corruption,
1016 the servers which provided the bad shares will be notified (via a
1017 file placed in the BASEDIR/storage/corruption-advisories directory)
1018 so their operators can manually delete the corrupted shares and
1019 investigate the problem. In addition, the "incident gatherer"
1020 mechanism will automatically report share corruption to an incident
1021 gatherer service, if one is configured. Note that corrupted shares
1022 indicate hardware failures, serious software bugs, or malice on the
1023 part of the storage server operator, so a corrupted share should be
1024 considered highly unusual.
1026 - By periodically checking/repairing all files and directories,
1027 objects in the Tahoe filesystem remain resistant to recoverability
1028 failures due to missing and/or broken servers.
1030 - This release includes a wapi mechanism to initiate checks on
1031 individual files and directories (with or without verification, and
1032 with or without automatic repair). A related mechanism is used to
1033 initiate a "deep-check" on a directory: recursively traversing the
1034 directory and its children, checking (and/or verifying/repairing)
1035 everything underneath. Both mechanisms can be run with an
1036 "output=JSON" argument, to obtain machine-readable check/repair
1037 status results. These results include a copy of the filesystem
1038 statistics from the "deep-stats" operation (including total number
1039 of files, size histogram, etc). If repair is possible, a "Repair"
1040 button will appear on the results page.
1042 - The client web interface now features some extra buttons to initiate
1043 check and deep-check operations. When these operations finish, they
1044 display a results page that summarizes any problems that were
1045 encountered. All long-running deep-traversal operations, including
1046 deep-check, use a start-and-poll mechanism, to avoid depending upon
1047 a single long-lived HTTP connection. `webapi.rst`_ has
1053 - The "tahoe backup" command is new in this release, which creates
1054 efficient versioned backups of a local directory. Given a local
1055 pathname and a target Tahoe directory, this will create a read-only
1056 snapshot of the local directory in $target/Archives/$timestamp. It
1057 will also create $target/Latest, which is a reference to the latest
1058 such snapshot. Each time you run "tahoe backup" with the same source
1059 and target, a new $timestamp snapshot will be added. These snapshots
1060 will share directories that have not changed since the last backup,
1061 to speed up the process and minimize storage requirements. In
1062 addition, a small database is used to keep track of which local
1063 files have been uploaded already, to avoid uploading them a second
1064 time. This drastically reduces the work needed to do a "null backup"
1065 (when nothing has changed locally), making "tahoe backup' suitable
1066 to run from a daily cronjob.
1068 Note that the "tahoe backup" CLI command must be used in conjunction
1069 with a 1.3.0-or-newer Tahoe client node; there was a bug in the
1070 1.2.0 webapi implementation that would prevent the last step (create
1071 $target/Latest) from working.
1076 - The 12GiB (approximate) immutable-file-size limitation is
1077 lifted. This release knows how to handle so-called "v2 immutable
1078 shares", which permit immutable files of up to about 18 EiB (about
1079 3*10^14). These v2 shares are created if the file to be uploaded is
1080 too large to fit into v1 shares. v1 shares are created if the file
1081 is small enough to fit into them, so that files created with
1082 tahoe-1.3.0 can still be read by earlier versions if they are not
1083 too large. Note that storage servers also had to be changed to
1084 support larger files, and this release is the first release in which
1085 they are able to do that. Clients will detect which servers are
1086 capable of supporting large files on upload and will not attempt to
1087 upload shares of a large file to a server which doesn't support it.
1092 - Tahoe now includes experimental FTP and SFTP servers. When
1093 configured with a suitable method to translate username+password
1094 into a root directory cap, it provides simple access to the virtual
1095 filesystem. Remember that FTP is completely unencrypted: passwords,
1096 filenames, and file contents are all sent over the wire in
1097 cleartext, so FTP should only be used on a local (127.0.0.1)
1098 connection. This feature is still in development: there are no unit
1099 tests yet, and behavior with respect to Unicode filenames is
1100 uncertain. Please see `FTP-and-SFTP.rst`_ for
1101 configuration details. (`#512`_, `#531`_)
1106 - This release adds the 'tahoe create-alias' command, which is a
1107 combination of 'tahoe mkdir' and 'tahoe add-alias'. This also allows
1108 you to start using a new tahoe directory without exposing its URI in
1109 the argv list, which is publicly visible (through the process table)
1110 on most unix systems. Thanks to Kevin Reid for bringing this issue
1113 - The single-argument form of "tahoe put" was changed to create an
1114 unlinked file. I.e. "tahoe put bar.txt" will take the contents of a
1115 local "bar.txt" file, upload them to the grid, and print the
1116 resulting read-cap; the file will not be attached to any
1117 directories. This seemed a bit more useful than the previous
1118 behavior (copy stdin, upload to the grid, attach the resulting file
1119 into your default tahoe: alias in a child named 'bar.txt').
1121 - "tahoe put" was also fixed to handle mutable files correctly: "tahoe
1122 put bar.txt URI:SSK:..." will read the contents of the local bar.txt
1123 and use them to replace the contents of the given mutable file.
1125 - The "tahoe webopen" command was modified to accept aliases. This
1126 means "tahoe webopen tahoe:" will cause your web browser to open to
1127 a "wui" page that gives access to the directory associated with the
1128 default "tahoe:" alias. It should also accept leading slashes, like
1129 "tahoe webopen tahoe:/stuff".
1131 - Many esoteric debugging commands were moved down into a "debug"
1134 - tahoe debug dump-cap
1135 - tahoe debug dump-share
1136 - tahoe debug find-shares
1137 - tahoe debug catalog-shares
1138 - tahoe debug corrupt-share
1140 The last command ("tahoe debug corrupt-share") flips a random bit
1141 of the given local sharefile. This is used to test the file
1142 verifying/repairing code, and obviously should not be used on user
1145 The cli might not correctly handle arguments which contain non-ascii
1146 characters in Tahoe v1.3 (although depending on your platform it
1147 might, especially if your platform can be configured to pass such
1148 characters on the command-line in utf-8 encoding). See
1149 http://tahoe-lafs.org/trac/tahoe/ticket/565 for details.
1154 - The "default webapi port", used when creating a new client node (and
1155 in the getting-started documentation), was changed from 8123 to
1156 3456, to reduce confusion when Tahoe accessed through a Firefox
1157 browser on which the "Torbutton" extension has been installed. Port
1158 8123 is occasionally used as a Tor control port, so Torbutton adds
1159 8123 to Firefox's list of "banned ports" to avoid CSRF attacks
1160 against Tor. Once 8123 is banned, it is difficult to diagnose why
1161 you can no longer reach a Tahoe node, so the Tahoe default was
1162 changed. Note that 3456 is reserved by IANA for the "vat" protocol,
1163 but there are argueably more Torbutton+Tahoe users than vat users
1164 these days. Note that this will only affect newly-created client
1165 nodes. Pre-existing client nodes, created by earlier versions of
1166 tahoe, may still be listening on 8123.
1168 - All deep-traversal operations (start-manifest, start-deep-size,
1169 start-deep-stats, start-deep-check) now use a start-and-poll
1170 approach, instead of using a single (fragile) long-running
1171 synchronous HTTP connection. All these "start-" operations use POST
1172 instead of GET. The old "GET manifest", "GET deep-size", and "POST
1173 deep-check" operations have been removed.
1175 - The new "POST start-manifest" operation, when it finally completes,
1176 results in a table of (path,cap), instead of the list of verifycaps
1177 produced by the old "GET manifest". The table is available in
1178 several formats: use output=html, output=text, or output=json to
1179 choose one. The JSON output also includes stats, and a list of
1180 verifycaps and storage-index strings. The "return_to=" and
1181 "when_done=" arguments have been removed from the t=check and
1182 deep-check operations.
1184 - The top-level status page (/status) now has a machine-readable form,
1185 via "/status/?t=json". This includes information about the
1186 currently-active uploads and downloads, which may be useful for
1187 frontends that wish to display progress information. There is no
1188 easy way to correlate the activities displayed here with recent wapi
1191 - Any files in BASEDIR/public_html/ (configurable) will be served in
1192 response to requests in the /static/ portion of the URL space. This
1193 will simplify the deployment of javascript-based frontends that can
1194 still access wapi calls by conforming to the (regrettable)
1195 "same-origin policy".
1197 - The welcome page now has a "Report Incident" button, which is tied
1198 into the "Incident Gatherer" machinery. If the node is attached to
1199 an incident gatherer (via log_gatherer.furl), then pushing this
1200 button will cause an Incident to be signalled: this means recent log
1201 events are aggregated and sent in a bundle to the gatherer. The user
1202 can push this button after something strange takes place (and they
1203 can provide a short message to go along with it), and the relevant
1204 data will be delivered to a centralized incident-gatherer for later
1205 processing by operations staff.
1207 - The "HEAD" method should now work correctly, in addition to the
1208 usual "GET", "PUT", and "POST" methods. "HEAD" is supposed to return
1209 exactly the same headers as "GET" would, but without any of the
1210 actual response body data. For mutable files, this now does a brief
1211 mapupdate (to figure out the size of the file that would be
1212 returned), without actually retrieving the file's contents.
1214 - The "GET" operation on files can now support the HTTP "Range:"
1215 header, allowing requests for partial content. This allows certain
1216 media players to correctly stream audio and movies out of a Tahoe
1217 grid. The current implementation uses a disk-based cache in
1218 BASEDIR/private/cache/download , which holds the plaintext of the
1219 files being downloaded. Future implementations might not use this
1220 cache. GET for immutable files now returns an ETag header.
1222 - Each file and directory now has a "Show More Info" web page, which
1223 contains much of the information that was crammed into the directory
1224 page before. This includes readonly URIs, storage index strings,
1225 object type, buttons to control checking/verifying/repairing, and
1226 deep-check/deep-stats buttons (for directories). For mutable files,
1227 the "replace contents" upload form has been moved here too. As a
1228 result, the directory page is now much simpler and cleaner, and
1229 several potentially-misleading links (like t=uri) are now gone.
1231 - Slashes are discouraged in Tahoe file/directory names, since they
1232 cause problems when accessing the filesystem through the
1233 wapi. However, there are a couple of accidental ways to generate
1234 such names. This release tries to make it easier to correct such
1235 mistakes by escaping slashes in several places, allowing slashes in
1236 the t=info and t=delete commands, and in the source (but not the
1237 target) of a t=rename command.
1242 - Tahoe's dependencies have been extended to require the
1243 "[secure_connections]" feature from Foolscap, which will cause
1244 pyOpenSSL to be required and/or installed. If OpenSSL and its
1245 development headers are already installed on your system, this can
1246 occur automatically. Tahoe now uses pollreactor (instead of the
1247 default selectreactor) to work around a bug between pyOpenSSL and
1248 the most recent release of Twisted (8.1.0). This bug only affects
1249 unit tests (hang during shutdown), and should not impact regular
1252 - The Tahoe source code tarballs now come in two different forms:
1253 regular and "sumo". The regular tarball contains just Tahoe, nothing
1254 else. When building from the regular tarball, the build process will
1255 download any unmet dependencies from the internet (starting with the
1256 index at PyPI) so it can build and install them. The "sumo" tarball
1257 contains copies of all the libraries that Tahoe requires (foolscap,
1258 twisted, zfec, etc), so using the "sumo" tarball should not require
1259 any internet access during the build process. This can be useful if
1260 you want to build Tahoe while on an airplane, a desert island, or
1261 other bandwidth-limited environments.
1263 - Similarly, tahoe-lafs.org now hosts a "tahoe-deps" tarball which
1264 contains the latest versions of all these dependencies. This
1266 http://tahoe-lafs.org/source/tahoe/deps/tahoe-deps.tar.gz, can be
1267 unpacked in the tahoe source tree (or in its parent directory), and
1268 the build process should satisfy its downloading needs from it
1269 instead of reaching out to PyPI. This can be useful if you want to
1270 build Tahoe from a darcs checkout while on that airplane or desert
1273 - Because of the previous two changes ("sumo" tarballs and the
1274 "tahoe-deps" bundle), most of the files have been removed from
1275 misc/dependencies/ . This brings the regular Tahoe tarball down to
1276 2MB (compressed), and the darcs checkout (without history) to about
1277 7.6MB. A full darcs checkout will still be fairly large (because of
1278 the historical patches which included the dependent libraries), but
1279 a 'lazy' one should now be small.
1281 - The default "make" target is now an alias for "setup.py build",
1282 which itself is an alias for "setup.py develop --prefix support",
1283 with some extra work before and after (see setup.cfg). Most of the
1284 complicated platform-dependent code in the Makefile was rewritten in
1285 Python and moved into setup.py, simplifying things considerably.
1287 - Likewise, the "make test" target now delegates most of its work to
1288 "setup.py test", which takes care of getting PYTHONPATH configured
1289 to access the tahoe code (and dependencies) that gets put in
1290 support/lib/ by the build_tahoe step. This should allow unit tests
1291 to be run even when trial (which is part of Twisted) wasn't already
1292 installed (in this case, trial gets installed to support/bin because
1293 Twisted is a dependency of Tahoe).
1295 - Tahoe is now compatible with the recently-released Python 2.6 ,
1296 although it is recommended to use Tahoe on Python 2.5, on which it
1297 has received more thorough testing and deployment.
1299 - Tahoe is now compatible with simplejson-2.0.x . The previous release
1300 assumed that simplejson.loads always returned unicode strings, which
1301 is no longer the case in 2.0.x .
1303 Grid Management Tools
1304 '''''''''''''''''''''
1306 - Several tools have been added or updated in the misc/ directory,
1307 mostly munin plugins that can be used to monitor a storage grid.
1309 - The misc/spacetime/ directory contains a "disk watcher" daemon
1310 (startable with 'tahoe start'), which can be configured with a set
1311 of HTTP URLs (pointing at the wapi '/statistics' page of a bunch of
1312 storage servers), and will periodically fetch
1313 disk-used/disk-available information from all the servers. It keeps
1314 this information in an Axiom database (a sqlite-based library
1315 available from divmod.org). The daemon computes time-averaged rates
1316 of disk usage, as well as a prediction of how much time is left
1317 before the grid is completely full.
1319 - The misc/munin/ directory contains a new set of munin plugins
1320 (tahoe_diskleft, tahoe_diskusage, tahoe_doomsday) which talk to the
1321 disk-watcher and provide graphs of its calculations.
1323 - To support the disk-watcher, the Tahoe statistics component
1324 (visible through the wapi at the /statistics/ URL) now includes
1325 disk-used and disk-available information. Both are derived through
1326 an equivalent of the unix 'df' command (i.e. they ask the kernel
1327 for the number of free blocks on the partition that encloses the
1328 BASEDIR/storage directory). In the future, the disk-available
1329 number will be further influenced by the local storage policy: if
1330 that policy says that the server should refuse new shares when less
1331 than 5GB is left on the partition, then "disk-available" will
1332 report zero even though the kernel sees 5GB remaining.
1334 - The 'tahoe_overhead' munin plugin interacts with an
1335 allmydata.com-specific server which reports the total of the
1336 'deep-size' reports for all active user accounts, compares this
1337 with the disk-watcher data, to report on overhead percentages. This
1338 provides information on how much space could be recovered once
1339 Tahoe implements some form of garbage collection.
1341 Configuration Changes: single INI-format tahoe.cfg file
1342 '''''''''''''''''''''''''''''''''''''''''''''''''''''''
1344 - The Tahoe node is now configured with a single INI-format file,
1345 named "tahoe.cfg", in the node's base directory. Most of the
1346 previous multiple-separate-files are still read for backwards
1347 compatibility (the embedded SSH debug server and the
1348 advertised_ip_addresses files are the exceptions), but new
1349 directives will only be added to tahoe.cfg . The "tahoe
1350 create-client" command will create a tahoe.cfg for you, with sample
1351 values commented out. (ticket `#518`_)
1353 - tahoe.cfg now has controls for the foolscap "keepalive" and
1354 "disconnect" timeouts (`#521`_).
1356 - tahoe.cfg now has controls for the encoding parameters:
1357 "shares.needed" and "shares.total" in the "[client]" section. The
1358 default parameters are still 3-of-10.
1360 - The inefficient storage 'sizelimit' control (which established an
1361 upper bound on the amount of space that a storage server is allowed
1362 to consume) has been replaced by a lightweight 'reserved_space'
1363 control (which establishes a lower bound on the amount of remaining
1364 space). The storage server will reject all writes that would cause
1365 the remaining disk space (as measured by a '/bin/df' equivalent) to
1366 drop below this value. The "[storage]reserved_space=" tahoe.cfg
1367 parameter controls this setting. (note that this only affects
1368 immutable shares: it is an outstanding bug that reserved_space does
1369 not prevent the allocation of new mutable shares, nor does it
1370 prevent the growth of existing mutable shares).
1375 - Clients now declare which versions of the protocols they
1376 support. This is part of a new backwards-compatibility system:
1377 http://tahoe-lafs.org/trac/tahoe/wiki/Versioning .
1379 - The version strings for human inspection (as displayed on the
1380 Welcome web page, and included in logs) now includes a platform
1381 identifer (frequently including a linux distribution name, processor
1384 - Several bugs have been fixed, including one that would cause an
1385 exception (in the logs) if a wapi download operation was cancelled
1386 (by closing the TCP connection, or pushing the "stop" button in a
1389 - Tahoe now uses Foolscap "Incidents", writing an "incident report"
1390 file to logs/incidents/ each time something weird occurs. These
1391 reports are available to an "incident gatherer" through the flogtool
1392 command. For more details, please see the Foolscap logging
1393 documentation. An incident-classifying plugin function is provided
1394 in misc/incident-gatherer/classify_tahoe.py .
1396 - If clients detect corruption in shares, they now automatically
1397 report it to the server holding that share, if it is new enough to
1398 accept the report. These reports are written to files in
1399 BASEDIR/storage/corruption-advisories .
1401 - The 'nickname' setting is now defined to be a UTF-8 -encoded string,
1402 allowing non-ascii nicknames.
1404 - The 'tahoe start' command will now accept a --syslog argument and
1405 pass it through to twistd, making it easier to launch non-Tahoe
1406 nodes (like the cpu-watcher) and have them log to syslogd instead of
1407 a local file. This is useful when running a Tahoe node out of a USB
1410 - The Mac GUI in src/allmydata/gui/ has been improved.
1412 .. _#512: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/512
1413 .. _#518: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/518
1414 .. _#521: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/521
1415 .. _#531: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/531
1417 Release 1.2.0 (2008-07-21)
1418 --------------------------
1423 - This release makes the immutable-file "ciphertext hash tree"
1424 mandatory. Previous releases allowed the uploader to decide whether
1425 their file would have an integrity check on the ciphertext or not. A
1426 malicious uploader could use this to create a readcap that would
1427 download as one file or a different one, depending upon which shares
1428 the client fetched first, with no errors raised. There are other
1429 integrity checks on the shares themselves, preventing a storage
1430 server or other party from violating the integrity properties of the
1431 read-cap: this failure was only exploitable by the uploader who
1432 gives you a carefully constructed read-cap. If you download the file
1433 with Tahoe 1.2.0 or later, you will not be vulnerable to this
1436 This change does not introduce a compatibility issue, because all
1437 existing versions of Tahoe will emit the ciphertext hash tree in
1443 - Tahoe now requires Foolscap-0.2.9 . It also requires pycryptopp 0.5
1444 or newer, since earlier versions had a bug that interacted with
1445 specific compiler versions that could sometimes result in incorrect
1446 encryption behavior. Both packages are included in the Tahoe source
1447 tarball in misc/dependencies/ , and should be built automatically
1453 - Web API directory pages should now contain properly-slash-terminated
1454 links to other directories. They have also stopped using absolute
1455 links in forms and pages (which interfered with the use of a
1456 front-end load-balancing proxy).
1458 - The behavior of the "Check This File" button changed, in conjunction
1459 with larger internal changes to file checking/verification. The
1460 button triggers an immediate check as before, but the outcome is
1461 shown on its own page, and does not get stored anywhere. As a
1462 result, the web directory page no longer shows historical checker
1465 - A new "Deep-Check" button has been added, which allows a user to
1466 initiate a recursive check of the given directory and all files and
1467 directories reachable from it. This can cause quite a bit of work,
1468 and has no intermediate progress information or feedback about the
1469 process. In addition, the results of the deep-check are extremely
1470 limited. A later release will improve this behavior.
1472 - The web server's behavior with respect to non-ASCII (unicode)
1473 filenames in the "GET save=true" operation has been improved. To
1474 achieve maximum compatibility with variously buggy web browsers, the
1475 server does not try to figure out the character set of the inbound
1476 filename. It just echoes the same bytes back to the browser in the
1477 Content-Disposition header. This seems to make both IE7 and Firefox
1480 Checker/Verifier/Repairer
1481 '''''''''''''''''''''''''
1483 - Tahoe is slowly acquiring convenient tools to check up on file
1484 health, examine existing shares for errors, and repair files that
1485 are not fully healthy. This release adds a mutable
1486 checker/verifier/repairer, although testing is very limited, and
1487 there are no web interfaces to trigger repair yet. The "Check"
1488 button next to each file or directory on the wapi page will perform
1489 a file check, and the "deep check" button on each directory will
1490 recursively check all files and directories reachable from there
1491 (which may take a very long time).
1493 Future releases will improve access to this functionality.
1495 Operations/Packaging
1496 ''''''''''''''''''''
1498 - A "check-grid" script has been added, along with a Makefile
1499 target. This is intended (with the help of a pre-configured node
1500 directory) to check upon the health of a Tahoe grid, uploading and
1501 downloading a few files. This can be used as a monitoring tool for a
1502 deployed grid, to be run periodically and to signal an error if it
1503 ever fails. It also helps with compatibility testing, to verify that
1504 the latest Tahoe code is still able to handle files created by an
1507 - The munin plugins from misc/munin/ are now copied into any generated
1508 debian packages, and are made executable (and uncompressed) so they
1509 can be symlinked directly from /etc/munin/plugins/ .
1511 - Ubuntu "Hardy" was added as a supported debian platform, with a
1512 Makefile target to produce hardy .deb packages. Some notes have been
1513 added to `debian.rst`_ about building Tahoe on a debian/ubuntu
1516 - Storage servers now measure operation rates and
1517 latency-per-operation, and provides results through the /statistics
1518 web page as well as the stats gatherer. Munin plugins have been
1524 - Tahoe nodes now use Foolscap "incident logging" to record unusual
1525 events to their NODEDIR/logs/incidents/ directory. These incident
1526 files can be examined by Foolscap logging tools, or delivered to an
1527 external log-gatherer for further analysis. Note that Tahoe now
1528 requires Foolscap-0.2.9, since 0.2.8 had a bug that complained about
1529 "OSError: File exists" when trying to create the incidents/
1530 directory for a second time.
1532 - If no servers are available when retrieving a mutable file (like a
1533 directory), the node now reports an error instead of hanging
1534 forever. Earlier releases would not only hang (causing the wapi
1535 directory listing to get stuck half-way through), but the internal
1536 dirnode serialization would cause all subsequent attempts to
1537 retrieve or modify the same directory to hang as well. `#463`_
1539 - A minor internal exception (reported in logs/twistd.log, in the
1540 "stopProducing" method) was fixed, which complained about
1541 "self._paused_at not defined" whenever a file download was stopped
1542 from the web browser end.
1544 .. _#463: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/463
1545 .. _#491: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/491
1546 .. _debian.rst: docs/debian.rst
1548 Release 1.1.0 (2008-06-11)
1549 --------------------------
1551 CLI: new "alias" model
1552 ''''''''''''''''''''''
1554 - The new CLI code uses an scp/rsync -like interface, in which
1555 directories in the Tahoe storage grid are referenced by a
1556 colon-suffixed alias. The new commands look like:
1558 - tahoe cp local.txt tahoe:virtual.txt
1559 - tahoe ls work:subdir
1561 - More functionality is available through the CLI: creating unlinked
1562 files and directories, recursive copy in or out of the storage grid,
1563 hardlinks, and retrieving the raw read- or write- caps through the
1564 'ls' command. Please read `CLI.rst`_ for complete details.
1566 wapi: new pages, new commands
1567 '''''''''''''''''''''''''''''
1569 - Several new pages were added to the web API:
1571 - /helper_status : to describe what a Helper is doing
1572 - /statistics : reports node uptime, CPU usage, other stats
1573 - /file : for easy file-download URLs, see `#221`_
1574 - /cap == /uri : future compatibility
1576 - The localdir=/localfile= and t=download operations were
1577 removed. These required special configuration to enable anyways, but
1578 this feature was a security problem, and was mostly obviated by the
1579 new "cp -r" command.
1581 - Several new options to the GET command were added:
1583 - t=deep-size : add up the size of all immutable files reachable from the directory
1584 - t=deep-stats : return a JSON-encoded description of number of files, size distribution, total size, etc
1586 - POST is now preferred over PUT for most operations which cause
1589 - Most wapi calls now accept overwrite=, and default to overwrite=true
1591 - "POST /uri/DIRCAP/parent/child?t=mkdir" is now the preferred API to
1592 create multiple directories at once, rather than ...?t=mkdir-p .
1594 - PUT to a mutable file ("PUT /uri/MUTABLEFILECAP", "PUT
1595 /uri/DIRCAP/child") will modify the file in-place.
1597 - more munin graphs in misc/munin/
1600 - tahoe-rootdir-space
1601 - tahoe_estimate_files
1602 - mutable files published/retrieved
1611 - setuptools (now required at runtime)
1613 New Mutable-File Code
1614 '''''''''''''''''''''
1616 - The mutable-file handling code (mostly used for directories) has
1617 been completely rewritten. The new scheme has a better API (with a
1618 modify() method) and is less likely to lose data when several
1619 uncoordinated writers change a file at the same time.
1621 - In addition, a single Tahoe process will coordinate its own
1622 writes. If you make two concurrent directory-modifying wapi calls to
1623 a single tahoe node, it will internally make one of them wait for
1624 the other to complete. This prevents auto-collision (`#391`_).
1626 - The new mutable-file code also detects errors during publish
1627 better. Earlier releases might believe that a mutable file was
1628 published when in fact it failed.
1633 - The node now monitors its own CPU usage, as a percentage, measured
1634 every 60 seconds. 1/5/15 minute moving averages are available on the
1635 /statistics web page and via the stats-gathering interface.
1637 - Clients now accelerate reconnection to all servers after being
1638 offline (`#374`_). When a client is offline for a long time, it
1639 scales back reconnection attempts to approximately once per hour, so
1640 it may take a while to make the first attempt, but once any attempt
1641 succeeds, the other server connections will be retried immediately.
1643 - A new "offloaded KeyGenerator" facility can be configured, to move
1644 RSA key generation out from, say, a wapi node, into a separate
1645 process. RSA keys can take several seconds to create, and so a wapi
1646 node which is being used for directory creation will be unavailable
1647 for anything else during this time. The Key Generator process will
1648 pre-compute a small pool of keys, to speed things up further. This
1649 also takes better advantage of multi-core CPUs, or SMP hosts.
1651 - The node will only use a potentially-slow "du -s" command at startup
1652 (to measure how much space has been used) if the "sizelimit"
1653 parameter has been configured (to limit how much space is
1654 used). Large storage servers should turn off sizelimit until a later
1655 release improves the space-management code, since "du -s" on a
1656 terabyte filesystem can take hours.
1658 - The Introducer now allows new announcements to replace old ones, to
1659 avoid buildups of obsolete announcements.
1661 - Immutable files are limited to about 12GiB (when using the default
1662 3-of-10 encoding), because larger files would be corrupted by the
1663 four-byte share-size field on the storage servers (`#439`_). A later
1664 release will remove this limit. Earlier releases would allow >12GiB
1665 uploads, but the resulting file would be unretrievable.
1667 - The docs/ directory has been rearranged, with old docs put in
1668 docs/historical/ and not-yet-implemented ones in docs/proposed/ .
1670 - The Mac OS-X FUSE plugin has a significant bug fix: earlier versions
1671 would corrupt writes that used seek() instead of writing the file in
1672 linear order. The rsync tool is known to perform writes in this
1673 order. This has been fixed.
1675 .. _#221: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/221
1676 .. _#374: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/374
1677 .. _#391: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/391
1678 .. _#439: http://tahoe-lafs.org/trac/tahoe-lafs/ticket/439
1679 .. _CLI.rst: docs/CLI.rst