ValueError (need more than 8 values to unpack) during mutable repair #1672
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#1672
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Situation:
Deep check was started from WUI on windows node(Windows Server 2008R2 if that's important).
I manually deleted some random shares in storage on one of other nodes(running Mac OS X if that's matter) and after that - stopped that other node.(I was checking how it will react to HDD failing)
Suddenly windows node's MUI deep check went to:
instead of check results
no incident file was autocreated
after that deep check for same directory was initiated on Mac OS X node
results mostly same
again no incident file was created
attempts to restart deep check results in same dump
Even though the results on Windows and Mac OS X are slightly different, it's unlikely that this is OS-specific; that's more likely to be nondeterminism due to timing, dict enumeration order, etc.
vikarti, is this with mutable.format set to mdmf?
Crash while repair on Windowsto ValueError (need more than 8 values to unpack) during repairValueError (need more than 8 values to unpack) during repairto ValueError (need more than 8 values to unpack) during mutable repairAssuming that this is a duplicate of #1669 due to the similarity of symptoms and error message. (That ticket also has a "RuntimeError: Request.finish called on a request after its connection was lost" in the log, but I suspect that may be a red herring.)