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