Reproducible UncoordinatedWriteError on repair

[ianchov]

Hi

Tahoe 1.9.1 (same with 1.9.0)

[ianchov@localhost]$ ./bin/tahoe deep-check --repair --add-lease -v XYZ:XYZ
'<root>': not healthy
 repair successful
ERROR: UncoordinatedWriteError()
"[Failure instance: Traceback (failure with no frames): <class 'allmydata.mutable.common.UncoordinatedWriteError'>: "

[davidsarah]

Is this problem reproducible, and does it happen without --add-lease?

[ianchov]

C:\Users\ianchov>C:\Python26\python.exe X:\allmydata-tahoe-1.9.1\bin\tahoe deep-
check --repair -v -d X:\tahoe cveti:
ERROR: UncoordinatedWriteError()
"[Failure instance: Traceback (failure with no frames): <class 'allmydata.mutabl
e.common.UncoordinatedWriteError'>: "


if is without repair and add-lease
C:\Users\ianchov>C:\Python26\python.exe X:\allmydata-tahoe-1.9.1\bin\tahoe deep-
check -v -d X:\tahoe XXXX:
'<root>': Unhealthy: some versions are unrecoverable
'Archives': Unhealthy: some versions are unrecoverable 10 shares (enc 5-of-12)
'Archives/2012-02-01_08:25:59Z': Not Healthy: 10 shares (enc 5-of-12)
'Archives/2012-02-01_08:25:59Z/Local Disk (C) - Shortcut.lnk': Not Healthy: 10 s
hares (enc 5-of-12).....

[kevan]

I don't think 1.9.1 has the fix for #1628. Can you try a deep check + repair with a Tahoe-LAFS that has that fix applied (preferably the current git master) and let us know if you can still reproduce the error?

[gyver]

Same problem here : "tahoe deep-check --add-lease" works on an alias but "tahoe deep-check --repair" throws UncoordinatedWriteError. See ticket #1656 for a probably related bug.

I separated the two to at least maintain my backups on the storage network waiting for a solution.

Unfortunately, I have to deploy the solution to 8 servers and for this I use gentoo ebuilds so testing git master is a bit tricky (although possible if time allows).

One note : one of my storage node had network connection problems which most probably happened during "tahoe cp" : I put very large tar.xz files that can take more than one hour to store. The problem started about the same time these connection issues happened.

[ianchov]

.....'Archives/2012-02-01_08:25:59Z/DESKTOP/Dokumentatsia_en.efektivnost_Kostinbrod/P
rilojenie_3_deklaracia 47,1.doc': not healthy
 repair successful
"ERROR: AttributeError('NoneType' object has no attribute 'callRemote')"
"[Failure instance: Traceback: <type 'exceptions.AttributeError'>: 'NoneType' ob
ject has no attribute 'callRemote'"
X:\allmydata-tahoe-1.9.1\support\Lib\site-packages\foolscap-0.6.3-py2.6.egg\fool
scap\call.py:677:_done
X:\allmydata-tahoe-1.9.1\support\Lib\site-packages\foolscap-0.6.3-py2.6.egg\fool
scap\call.py:60:complete
X:\allmydata-tahoe-1.9.1\support\Lib\site-packages\twisted-10.1.0-py2.6-win-amd6
4.egg\twisted\internet\defer.py:318:callback
X:\allmydata-tahoe-1.9.1\support\Lib\site-packages\twisted-10.1.0-py2.6-win-amd6
4.egg\twisted\internet\defer.py:424:_startRunCallbacks
--- <exception caught here> ---
X:\allmydata-tahoe-1.9.1\support\Lib\site-packages\twisted-10.1.0-py2.6-win-amd6
4.egg\twisted\internet\defer.py:441:_runCallbacks
x:\allmydata-tahoe-1.9.1\src\allmydata\immutable\upload.py:553:_got_response
x:\allmydata-tahoe-1.9.1\src\allmydata\immutable\upload.py:420:_loop
x:\allmydata-tahoe-1.9.1\src\allmydata\immutable\upload.py:105:query

C:\Users\ianchov>C:\Python26\python.exe X:\allmydata-tahoe-1.9.1\bin\tahoe deep-
check --repair --add-lease -v -d X:\tahoe cveti:
'<root>': not healthy
 repair successful
ERROR: UncoordinatedWriteError()
"[Failure instance: Traceback (failure with no frames): <class 'allmydata.mutabl
e.common.UncoordinatedWriteError'>: "

C:\Users\ianchov>C:\Python26\python.exe X:\allmydata-tahoe-1.9.1\bin\tahoe deep-
check --repair --add-lease -v -d X:\tahoe cveti:
'<root>': not healthy
 repair successful
ERROR: UncoordinatedWriteError()
"[Failure instance: Traceback (failure with no frames): <class 'allmydata.mutabl
e.common.UncoordinatedWriteError'>: "