The Tahoe-LAFS decentralized secure filesystem.
0c25628ded
using both small and large blocksizes for writes, write a 1Mb file to fuse where every write overlaps another. This serves a useful purpose - in manual testing of blackmatch some time ago most operations e.g. bulk copies, worked fine, but using rsync caused data corruption on most files. it turned out to be that rsync writes in 64K blocks, but rather than making the last block short, the last block instead overlaps the preceding (already written) block. This revealed a problem where cache files were being opened 'append' rather than 'write' and hence the overlapping write to the fuse layer caused the overlapping portion of the file to be duplicated in cache, leading to oversized and corrupt files being uploaded. |
||
|---|---|---|
| bin | ||
| contrib | ||
| docs | ||
| mac | ||
| misc | ||
| src/allmydata | ||
| twisted/plugins | ||
| windows | ||
| _auto_deps.py | ||
| .darcs-boringfile | ||
| COPYING.GPL | ||
| COPYING.TGPPL.html | ||
| CREDITS | ||
| ez_setup.py | ||
| Makefile | ||
| NEWS | ||
| README | ||
| relnotes.txt | ||
| setup.cfg | ||
| setup.py | ||
| Tahoe.home | ||
Welcome to the Tahoe project [1], a secure, decentralized, fault-tolerant filesystem. All of the source code is available under a Free Software, Open Source licence (or two). Please see docs/about.html for an introduction, docs/install.html for install instructions, docs/running.html for usage instructions. Finally, see docs/known_issues.txt for things that you need to know about if you are relying on Tahoe to store your valuable data. [1] http://allmydata.org