[tahoe-lafs-trac-stream] [tahoe-lafs] #1628: UCWE on deep check with recent version
tahoe-lafs
trac at tahoe-lafs.org
Thu Dec 1 00:04:32 UTC 2011
#1628: UCWE on deep check with recent version
--------------------------+------------------------------------------------
Reporter: | Owner: somebody
davidsarah | Status: new
Type: defect | Milestone: undecided
Priority: major | Version: 1.9.0
Component: code | Keywords: tahoe-check verify ucwe regression
Resolution: |
Launchpad Bug: |
--------------------------+------------------------------------------------
Description changed by kpreid:
Old description:
> [https://tahoe-lafs.org/pipermail/tahoe-dev/2011-November/006870.html
> Reported by kpreid]:
> I upgraded my tahoe to a recent development version, in the git mirror:
> {{{
> git://github.com/warner/tahoe-lafs.git
> commit b73aba98de93c4c0b0013f1dd435c64e73e48f4c
> }}}
>
> Now, my daily deep-check --repair --add-lease on my four aliases on the
> volunteer grid consistently fails as follows. The first might have a
> legitimate uncoordinated write, but the last two are not regularly
> touched by anything but the repair process, and this identical failure
> has occurred for the past 4 days.
>
> I'd appreciate it if this is fixed before my leases expire. :-)
> {{{
> -----------------------------------------------------------------------
> ERROR: UncoordinatedWriteError()
> "[Failure instance: Traceback (failure with no frames): <class
> 'allmydata.mutable.common.UncoordinatedWriteError'>: "
>
> ERROR: AssertionError()
> "[Failure instance: Traceback: <type 'exceptions.AssertionError'>: "
> /Volumes/Opp/External/Projects/tahoe/src/allmydata/mutable/filenode.py:563:upload
> /Volumes/Opp/External/Projects/tahoe/src/allmydata/mutable/filenode.py:661:_do_serialized
> /Volumes/Opp/External/Projects/tahoe/support/lib/python2.6/site-
> packages/Twisted-11.1.0-py2.6-macosx-10.6-x86_64.egg/twisted/internet/defer.py:298:addCallback
> /Volumes/Opp/External/Projects/tahoe/support/lib/python2.6/site-
> packages/Twisted-11.1.0-py2.6-macosx-10.6-x86_64.egg/twisted/internet/defer.py:287:addCallbacks
> --- <exception caught here> ---
> /Volumes/Opp/External/Projects/tahoe/support/lib/python2.6/site-
> packages/Twisted-11.1.0-py2.6-macosx-10.6-x86_64.egg/twisted/internet/defer.py:545:_runCallbacks
> /Volumes/Opp/External/Projects/tahoe/src/allmydata/mutable/filenode.py:661:<lambda>
> /Volumes/Opp/External/Projects/tahoe/src/allmydata/mutable/filenode.py:689:_upload
> /Volumes/Opp/External/Projects/tahoe/src/allmydata/mutable/publish.py:402:publish
>
> ERROR: UncoordinatedWriteError()
> "[Failure instance: Traceback (failure with no frames): <class
> 'allmydata.mutable.common.UncoordinatedWriteError'>: "
>
> ERROR: UncoordinatedWriteError()
> "[Failure instance: Traceback (failure with no frames): <class
> 'allmydata.mutable.common.UncoordinatedWriteError'>: "
> -----------------------------------------------------------------------
> }}}
> Before these failures, here is a typical example of normal results. (The
> indentation is added by my script.) I had understood the post-repair
> unhealthiness to be due to disagreement between the "healthy file" and
> "repair (successful re-upload)", a to-be-fixed bug.
> {{{
> -----------------------------------------------------------------------
> done: 3 objects checked
> pre-repair: 3 healthy, 0 unhealthy
> 0 repairs attempted, 0 successful, 0 failed
> post-repair: 3 healthy, 0 unhealthy
>
> repair successful
> done: 1 objects checked
> pre-repair: 0 healthy, 1 unhealthy
> 1 repairs attempted, 1 successful, 0 failed
> post-repair: 0 healthy, 1 unhealthy
>
> repair successful
> done: 5 objects checked
> pre-repair: 4 healthy, 1 unhealthy
> 1 repairs attempted, 1 successful, 0 failed
> post-repair: 4 healthy, 1 unhealthy
>
> repair successful
> done: 5 objects checked
> pre-repair: 4 healthy, 1 unhealthy
> 1 repairs attempted, 1 successful, 0 failed
> post-repair: 4 healthy, 1 unhealthy
> }}}
New description:
[https://tahoe-lafs.org/pipermail/tahoe-dev/2011-November/006870.html
Reported by kpreid]:
I upgraded my tahoe to a recent development version, in the git mirror:
{{{
git://github.com/warner/tahoe-lafs.git
commit b73aba98de93c4c0b0013f1dd435c64e73e48f4c
}}}
Now, my daily deep-check --repair --add-lease on my four aliases on the
volunteer grid consistently fails as follows. The first might have a
legitimate uncoordinated write, but the last two are not regularly touched
by anything but the repair process, and this identical failure has
occurred for the past 4 days.
I'd appreciate it if this is fixed before my leases expire. :-)
{{{
ERROR: UncoordinatedWriteError()
"[Failure instance: Traceback (failure with no frames): <class
'allmydata.mutable.common.UncoordinatedWriteError'>: "
ERROR: AssertionError()
"[Failure instance: Traceback: <type 'exceptions.AssertionError'>: "
/Volumes/Opp/External/Projects/tahoe/src/allmydata/mutable/filenode.py:563:upload
/Volumes/Opp/External/Projects/tahoe/src/allmydata/mutable/filenode.py:661:_do_serialized
/Volumes/Opp/External/Projects/tahoe/support/lib/python2.6/site-
packages/Twisted-11.1.0-py2.6-macosx-10.6-x86_64.egg/twisted/internet/defer.py:298:addCallback
/Volumes/Opp/External/Projects/tahoe/support/lib/python2.6/site-
packages/Twisted-11.1.0-py2.6-macosx-10.6-x86_64.egg/twisted/internet/defer.py:287:addCallbacks
--- <exception caught here> ---
/Volumes/Opp/External/Projects/tahoe/support/lib/python2.6/site-
packages/Twisted-11.1.0-py2.6-macosx-10.6-x86_64.egg/twisted/internet/defer.py:545:_runCallbacks
/Volumes/Opp/External/Projects/tahoe/src/allmydata/mutable/filenode.py:661:<lambda>
/Volumes/Opp/External/Projects/tahoe/src/allmydata/mutable/filenode.py:689:_upload
/Volumes/Opp/External/Projects/tahoe/src/allmydata/mutable/publish.py:402:publish
ERROR: UncoordinatedWriteError()
"[Failure instance: Traceback (failure with no frames): <class
'allmydata.mutable.common.UncoordinatedWriteError'>: "
ERROR: UncoordinatedWriteError()
"[Failure instance: Traceback (failure with no frames): <class
'allmydata.mutable.common.UncoordinatedWriteError'>: "
}}}
Before these failures, here is a typical example of normal results. (The
indentation is added by my script.) I had understood the post-repair
unhealthiness to be due to disagreement between the "healthy file" and
"repair (successful re-upload)", a to-be-fixed bug.
{{{
done: 3 objects checked
pre-repair: 3 healthy, 0 unhealthy
0 repairs attempted, 0 successful, 0 failed
post-repair: 3 healthy, 0 unhealthy
repair successful
done: 1 objects checked
pre-repair: 0 healthy, 1 unhealthy
1 repairs attempted, 1 successful, 0 failed
post-repair: 0 healthy, 1 unhealthy
repair successful
done: 5 objects checked
pre-repair: 4 healthy, 1 unhealthy
1 repairs attempted, 1 successful, 0 failed
post-repair: 4 healthy, 1 unhealthy
repair successful
done: 5 objects checked
pre-repair: 4 healthy, 1 unhealthy
1 repairs attempted, 1 successful, 0 failed
post-repair: 4 healthy, 1 unhealthy
}}}
--
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1628#comment:2>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list