tahoe backup error #1656
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#1656
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?
Hi guys
i do my backup with
I have the very same exception (KeyError), happening at the same spot ( shares = versionmapself.verinfo ). I use tahoe cp for my backups though. I can replicate this as soon as I try to backup a file in one of two directories which are direct subdirs of an alias I can't "tahoe deep-check --repair" anymore (I'll open a separate bug).
The file being cp'ed is correctly created and can be retrieved intact even though tahoe receives a 500 error.
On the same private tahoe storage network another alias doesn't have this problem : I can tahoe cp and repair without errors so I guess the problem is either at the alias or both of its 2 subdirs.
Note that I tahoe cp huge files and sometimes one flaky storage node ADSL provider can break the connection in middle of a transfer.
Replying to gyver:
couldn't find out how to attach an incident file, uploading one returns me to a page asking me if I want to add other attachments...
Duplicate of #1670 (since the KeyError occurs on the same line).
gyver: that problem can happen if the attachment is too large. How large is the file? Can you host it somewhere else?
(You can reply here even though this bug is closed as a duplicate.)
The problem isn't due to the file size : I manage to backup files up to 3GB on the same storage network from the same point but in other directories and the failures happen with 8MB files.
Replying to gyver:
Oops, I think I just understood which attachment you were referring to. The incident file was around 40kB IIRC. I'll host it somewhere.
Here is an incident file for the tahoe put
http://www.bouton.name/incident-2012-02-18--22_00_17Z-7jusaxa.flog.bz2
Here is an incident file for the tahoe deep-check --repair in the same problematic "tree"
http://www.bouton.name/incident-2012-02-18--22_59_20Z-fsyvi7q.flog.bz2
(http://www.bouton.name/incident-2012-02-18--22_00_17Z-7jusaxa.flog.bz2) gives me a 403 Forbidden (probably incorrect file permissions).
Sorry, I plead exhaustion: apparently I did chmod a+x instead of a+r for this one... Fixed.
Okay, I've attached those files to #1670. Thanks.
Ok
The error dissappeard as long i just change the shares.total = 15
before it was to 12...
????