id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	launchpad_bug
1583	Failure: allmydata.mutable.common.UncoordinatedWriteError	killyourtv	kevan	"I have patched my installation of tahoe 1.9.0 with the patch from ticket #1010 (which worked perfectly with v1.8.3) for use on the I2P network.

Trying to repair my share I get the following error:


{{{
$ tahoe check --repair tahoe:
ERROR: 500 Internal Server Error
""Traceback (most recent call last):\x0aFailure: allmydata.mutable.common.UncoordinatedWriteError: \x0a""

}}}

This error will show no matter how many times the command is re-run. (I tried re-running it 10 times and the error came up each time).

After reverting back to v1.8.3:


{{{
$ tahoe check --repair tahoe:
Summary: not healthy
 storage index: ft4svdmjfm5th3sunuh6hhfcma
 good-shares: 4 (encoding is 3-of-10)
 wrong-shares: 5
 repair successful
}}}


Running the command again:


{{{
$ tahoe check --repair tahoe:
Summary: healthy
 storage index: ft4svdmjfm5th3sunuh6hhfcma
 good-shares: 10 (encoding is 3-of-10)
 wrong-shares: 0

}}}

A deep-check is currently running on the share using v1.8.3.

The used packages:

{{{

foolscap: 0.6.2,
pycryptopp: 0.5.29,
zfec: 1.4.22,
Twisted: 11.0.0,
Nevow: 0.10.0,
zope.interface: unknown,
python: 2.7.2+,
platform: Linux-debian_wheezy/sid-x86_64-64bit_ELF,
pyOpenSSL: 0.13,
simplejson: 2.2.0,
pycrypto: 2.4,
pyasn1: unknown,
mock: 0.7.2,
sqlite3: 2.6.0 [sqlite 3.7.9],
setuptools: 0.6 [distribute]

}}}

Please let me know if any other info would be of use."	defect	closed	critical	undecided	unknown	1.9.0	duplicate	UncoordinatedWriteError ucwe regression	zooko