[tahoe-dev] Deep-check --repair issues

[Nathan Eisenberg]

> Huh. What version are you running? If you run it without the --repair
> option, does it see all the files?

Nope, it seems to die:

tintro:~# tahoe ls test:Archives
2009-12-04_08:46:08Z
2009-12-04_08:46:10Z
2009-12-04_08:46:12Z

tintro:~# tahoe deep-check -v test:Archives
<root>: Unhealthy: 8 shares (enc 3-of-10)
2009-12-04_08:46:08Z: Unhealthy: 8 shares (enc 3-of-10)
done: 2 objects checked, 0 healthy, 2 unhealthy

Version:

allmydata-tahoe: 1.5.0, foolscap: 0.4.2, pycryptopp: 0.5.17, zfec: 1.4.5, Twisted: 8.2.0, Nevow: 0.9.31, zope.interface: 3.3.1, python: 2.5.2, platform: Linux-debian_5.0.3-x86_64-64bit, sqlite: 3.5.9, simplejson: 1.9.2, argparse: 0.9.1, pyOpenSSL: 0.7, pyutil: 1.3.34, zbase32: 1.1.1, setuptools: 0.6c12dev, pysqlite: 2.3.2

This is a test cluster with test data.  I haven't implemented backups using this method yet, so it's not a real problem for me.

Just so I understand (I'm still new to tahoe and looking for ways to validate what I've learned so far): 

*2009-12-04_08:46:08Z is a link to the read-only cap of a mutable folder (presumably this was done pre-immutable folders as a way of protecting them).  **Read only does not confer the ability to repair a file
***Therefore the repair fails, killing the script.

Best Regards,
Nathan Eisenberg