backup stopped with "UnrecoverableFileError:" #2482
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
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#2482
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
The tail end of the output from
time tahoe backup -v -v -v . papers:
is:The version of Tahoe-LAFS is:
Attachment flog-catchup.flog (242436 bytes) added
I just uploaded flog-catchup.flog, which resulted from using this command:
time tahoe debug flogtool tail --verbose --catch-up --save-to=flog-catchup.flog --timestamps=utc ~/.tahoe/private/logport.furl
. If you look at that file withflogtool dump --timestamps=utc
, it outputs this:I then started a flogtool tail going with this command:
tahoe debug flogtool tail --verbose --save-to=flog-tail.flog --timestamps=utc ~/.tahoe/private/logport.furl
, and then I re-ran the exact sametahoe backup
command, like this:time tahoe backup -v -v -v . papers:
. This time the tail of the output of thetahoe backup
command was this:And the resulting flog tail file (which I will attach to this ticket), dumps to this:
Note, that's the complete output of the dump — only 43 lines.
Attachment flog-tail-2.flog (8991 bytes) added
I clicked the "report an incident" button and it generated
incident-2015-08-14--21-27-34Z-tvkqqwy.flog.bz2
Attachment incident-2015-08-14--21-27-34Z-tvkqqwy.flog.bz2 (17621 bytes) added
I updated to current git HEAD and re-ran the test and got the same result.
tahoe version
now says:Then I tried a
deep-check
. The stdout was:I'll attach the flog tail and the incident report file that I generated by the "report an incident" button.
Attachment incident-2015-08-14--21-58-50Z-oxrfsra.flog.bz2 (10087 bytes) added
Attachment flog-tail-5.flog (8476 bytes) added
I used
tahoe debug dump-cap
to get more information about the root directory which is the one that is unrecoverable according to that deep-check output from comment:98060:Is
drop_upload enabled
set to true intahoe.cfg
? Try setting it to false. (This might be unrelated to the backup error, but I want to eliminate it from consideration if so.)I unset that setting and reproduced the issue — same behavior after drop upload was disabled.
This was due to Zooko's TLoS3 subscription having been cancelled.