tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

Folder healthy, but still get 410 Gone #1916

New issue
Open
opened 2013-02-06 22:41:36 +00:00 by PRabahy · 11 comments
PRabahy commented 2013-02-06 22:41:36 +00:00
Owner
Copy link

I tried to add copy an item to the public folder on the public grid but received an error. I am able to "ls" the directory and when I run "check" it says it is healthy, but when I try to upload it errors out.

Trace from command line:

C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe ls public:
DNSBench.exe
PreviousGridPublicDirectory
ThisDirectoryWritecap-RecursiveLOL
bitcoin-0.7.2-win32-setup.exe
diskcryptor.7z
multibit-0.4.19-windows.exe
python-2.7.3.msi
test_for_martin
thanks!.txt

C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe check --repair public:
Summary: healthy
 storage index: txm5k7xe52cw3d4kny372i46ly
 good-shares: 10 (encoding is 1-of-10)
 wrong-shares: 0

C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe cp "C:\Users\paul.rabahy\Downloads\Provable Data Possession at !UntrustedStores.pdf" public:
Error examining target directory: 410 Gone
UnrecoverableFileError: the directory (or mutable file) could not be retrieved, because there were insufficient good shares. This might indicate that no servers were connected, insufficient servers were connected, the URI was corrupt, or that shares have been lost due to server departure, hard drive failure, or disk corruption. You should perform a filecheck on this object to learn more.
I tried to add copy an item to the public folder on the public grid but received an error. I am able to "ls" the directory and when I run "check" it says it is healthy, but when I try to upload it errors out. Trace from command line: ``` C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe ls public: DNSBench.exe PreviousGridPublicDirectory ThisDirectoryWritecap-RecursiveLOL bitcoin-0.7.2-win32-setup.exe diskcryptor.7z multibit-0.4.19-windows.exe python-2.7.3.msi test_for_martin thanks!.txt C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe check --repair public: Summary: healthy storage index: txm5k7xe52cw3d4kny372i46ly good-shares: 10 (encoding is 1-of-10) wrong-shares: 0 C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe cp "C:\Users\paul.rabahy\Downloads\Provable Data Possession at !UntrustedStores.pdf" public: Error examining target directory: 410 Gone UnrecoverableFileError: the directory (or mutable file) could not be retrieved, because there were insufficient good shares. This might indicate that no servers were connected, insufficient servers were connected, the URI was corrupt, or that shares have been lost due to server departure, hard drive failure, or disk corruption. You should perform a filecheck on this object to learn more. ```
tahoe-lafs added the
unknown
normal
defect
1.9.2
 labels 2013-02-06 22:41:36 +00:00
tahoe-lafs added this to the undecided milestone 2013-02-06 22:41:36 +00:00
PRabahy commented 2013-02-08 14:40:14 +00:00
Author
Owner
Copy link

Improved readability of ticket.

Improved readability of ticket.
zooko commented 2013-02-10 12:15:26 +00:00
Author
Owner
Copy link

escape "wiki words"

escape "wiki words"
zooko commented 2013-02-10 12:16:20 +00:00
Author
Owner
Copy link

quote literals

quote literals
zooko commented 2013-02-10 12:32:43 +00:00
Author
Owner
Copy link

Dear PRabahy:

Thank you for reporting this!

This seems like a bug which has pretty bad consequences for availability. It doesn't ring a bell -- I don't remember seeing this sort of misbehavior reported before. Is it consistently reproducible, or does the behavior sometimes vary? Are there any incident report files in the gateway's base directory? Please see wiki/HowToReportABug. Thanks!

Dear PRabahy: Thank you for reporting this! This seems like a bug which has pretty bad consequences for availability. It doesn't ring a bell -- I don't remember seeing this sort of misbehavior reported before. Is it consistently reproducible, or does the behavior sometimes vary? Are there any incident report files in the gateway's base directory? Please see [wiki/HowToReportABug](wiki/HowToReportABug). Thanks!
PRabahy commented 2013-02-11 13:40:00 +00:00
Author
Owner
Copy link

The bug was reproducible at the time. I tried the upload several times before I ended up the with trace that I posted above. Unfortunately, I just tried it again and now the "cp" works just fine now.

I don't see any incident reports and have already restarted the node. If it happens again, I will make sure to grab/post a log.

The bug was reproducible at the time. I tried the upload several times before I ended up the with trace that I posted above. Unfortunately, I just tried it again and now the "cp" works just fine now. I don't see any incident reports and have already restarted the node. If it happens again, I will make sure to grab/post a log.
davidsarah commented 2013-02-11 21:38:07 +00:00
Author
Owner
Copy link

It's quite possible that a modification to the public directory by another gateway resolved whatever condition was causing the modification by PRabahy's gateway to fail. In that case, I'm not very hopeful of finding out what was wrong :-(

It's quite possible that a modification to the public directory by another gateway resolved whatever condition was causing the modification by PRabahy's gateway to fail. In that case, I'm not very hopeful of finding out what was wrong :-(
tahoe-lafs added
code-mutable
 and removed
unknown
 labels 2013-02-11 21:38:07 +00:00
PRabahy commented 2013-02-12 19:17:56 +00:00
Author
Owner
Copy link

Attachment incident-2013-02-12--19-13-04Z-ejgqrja.flog (602105 bytes) added

**Attachment** incident-2013-02-12--19-13-04Z-ejgqrja.flog (602105 bytes) added
incident-2013-02-12--19-13-04Z-ejgqrja.flog
588 KiB
PRabahy commented 2013-02-12 19:32:15 +00:00
Author
Owner
Copy link

I think it is happening again. I don't know if this is relevant or not, but I noticed that the node that originally made the directory is offline.

This time, I can do "ls", but "stat" and "cp" are returning 410.

C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe ls public:
CryptoResearch
DNSBench.exe
FileZilla_3.6.0.2_win32-setup.exe
bitcoin-0.7.2-win32-setup.exe
cahewson-test
multibit-0.4.19-windows.exe
polipo.1
python-2.7.3.msi
test.jpg
test_for_martin
test_for_martin-readonly

C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe check public:
Summary: Unhealthy: 7 shares (enc 1-of-10)
 storage index: txm5k7xe52cw3d4kny372i46ly
 good-shares: 7 (encoding is 1-of-10)
 wrong-shares: 0

C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe stats public:
ERROR: 410 Gone
UnrecoverableFileError: the directory (or mutable file) could not be retrieved,
because there were insufficient good shares. This might indicate that no servers
 were connected, insufficient servers were connected, the URI was corrupt, or th
at shares have been lost due to server departure, hard drive failure, or disk co
rruption. You should perform a filecheck on this object to learn more.

C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe cp C:\Windows\Med
ia\onestop.mid public:
Error examining target directory: 410 Gone
UnrecoverableFileError: the directory (or mutable file) could not be retrieved,
because there were insufficient good shares. This might indicate that no servers
 were connected, insufficient servers were connected, the URI was corrupt, or th
at shares have been lost due to server departure, hard drive failure, or disk co
rruption. You should perform a filecheck on this object to learn more.

I am trying to run "check --repair" but it appears to have hung for about 10-15 minutes, so I'm not sure if it is stuck.

I think it is happening again. I don't know if this is relevant or not, but I noticed that the node that originally made the directory is offline. This time, I can do "ls", but "stat" and "cp" are returning 410. ``` C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe ls public: CryptoResearch DNSBench.exe FileZilla_3.6.0.2_win32-setup.exe bitcoin-0.7.2-win32-setup.exe cahewson-test multibit-0.4.19-windows.exe polipo.1 python-2.7.3.msi test.jpg test_for_martin test_for_martin-readonly C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe check public: Summary: Unhealthy: 7 shares (enc 1-of-10) storage index: txm5k7xe52cw3d4kny372i46ly good-shares: 7 (encoding is 1-of-10) wrong-shares: 0 C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe stats public: ERROR: 410 Gone UnrecoverableFileError: the directory (or mutable file) could not be retrieved, because there were insufficient good shares. This might indicate that no servers were connected, insufficient servers were connected, the URI was corrupt, or th at shares have been lost due to server departure, hard drive failure, or disk co rruption. You should perform a filecheck on this object to learn more. C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe cp C:\Windows\Med ia\onestop.mid public: Error examining target directory: 410 Gone UnrecoverableFileError: the directory (or mutable file) could not be retrieved, because there were insufficient good shares. This might indicate that no servers were connected, insufficient servers were connected, the URI was corrupt, or th at shares have been lost due to server departure, hard drive failure, or disk co rruption. You should perform a filecheck on this object to learn more. ``` I am trying to run "check --repair" but it appears to have hung for about 10-15 minutes, so I'm not sure if it is stuck.
PRabahy commented 2013-02-12 20:08:21 +00:00
Author
Owner
Copy link

"check --repair" finally finished. It said that it was successful, but that the directory was still unhealthy (bug?). I then ran "ls" and another "check"

C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe check --repair pu
blic:
Summary: not healthy
 storage index: txm5k7xe52cw3d4kny372i46ly
 good-shares: 5 (encoding is 1-of-10)
 wrong-shares: 0
 repair successful

C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe ls public:
CryptoResearch
DNSBench.exe
FileZilla_3.6.0.2_win32-setup.exe
bitcoin-0.7.2-win32-setup.exe
cahewson-test
multibit-0.4.19-windows.exe
polipo.1
python-2.7.3.msi
test.jpg
test_for_martin
test_for_martin-readonly

C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe check public:
Summary: Unhealthy: multiple versions are recoverable
 storage index: txm5k7xe52cw3d4kny372i46ly
 good-shares: 10 (encoding is 1-of-10)
 wrong-shares: 5

Every time I check, there are 2 storage nodes that appear online (according to the WUI).

"check --repair" finally finished. It said that it was successful, but that the directory was still unhealthy (bug?). I then ran "ls" and another "check" ``` C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe check --repair pu blic: Summary: not healthy storage index: txm5k7xe52cw3d4kny372i46ly good-shares: 5 (encoding is 1-of-10) wrong-shares: 0 repair successful C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe ls public: CryptoResearch DNSBench.exe FileZilla_3.6.0.2_win32-setup.exe bitcoin-0.7.2-win32-setup.exe cahewson-test multibit-0.4.19-windows.exe polipo.1 python-2.7.3.msi test.jpg test_for_martin test_for_martin-readonly C:\Users\paul.rabahy\Downloads\allmydata-tahoe-1.9.2\bin>tahoe check public: Summary: Unhealthy: multiple versions are recoverable storage index: txm5k7xe52cw3d4kny372i46ly good-shares: 10 (encoding is 1-of-10) wrong-shares: 5 ``` Every time I check, there are 2 storage nodes that appear online (according to the WUI).
PRabahy commented 2013-02-12 20:09:15 +00:00
Author
Owner
Copy link

Attachment incident-2013-02-12--20-08-28Z-y7lgyki.flog (636848 bytes) added

**Attachment** incident-2013-02-12--20-08-28Z-y7lgyki.flog (636848 bytes) added
incident-2013-02-12--20-08-28Z-y7lgyki.flog
622 KiB
zooko commented 2013-02-13 19:16:53 +00:00
Author
Owner
Copy link

Good job capturing evidence when the problem recurred, PRabahy!

Good job capturing evidence when the problem recurred, PRabahy!
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
No results found.
No results found.
Labels
Clear labels   
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

catch-all for anything that can be fixed by writing code but isn't classified better

  
code-dirnodes

anything involving tahoe directories

  
code-encoding

immutable-file encoding format/layout, cap format, encoding/decoding algorithms

  
code-frontend

general frontend things: new user-facing interfaces, FTP/SFTP servers, FUSE-like interfaces

  
code-frontend-cli

CLI tools

  
code-frontend-ftp-sftp

   
code-frontend-magic-folder

   
code-frontend-web

webapi interfaces, user-facing "WUI" interfaces

  
code-mutable

anything involving mutable files: encoding/decoding, share format

  
code-network

Introducer, locating storage servers, establishing/maintaining connections to them

  
code-nodeadmin

node startup/shutdown, tools to create nodes, logging tools, management/monitoring tools, manhole, disk-space-limiting tools

  
code-peerselection

server selection/sorting algorithm, rebalancing code, allocation policy, swarming-download

  
code-storage

storage-server implementation, share-storage directory layout, client-to-server share transfer protocol

  
contrib

problems with non-core things that live in the source:contrib/ directory

  
critical

   
defect

   
dev-infrastructure

things that help us build Tahoe: buildbot, automated speed/memory/code-coverage tests and results-displayers, IRC channels, mailing lists, this Trac instance

  
documentation

docs items. Also use 'docs' keyword on tickets in more specific components.

  
duplicate

   
enhancement

   
fixed

   
invalid

   
major

   
minor

   
n/a

   
normal

   
operational

things involved in running a tahoe grid, external tools to monitor/maintain a grid (like "nodeadmin" but larger-scale). Was also used for issues with the allmydata.com grid.

  
packaging

setup.py script, library dependencies, binary packages, licensing, installation instructions

  
somebody else's problem

   
supercritical

   
task

   
trivial

   
unknown

Uncategorized. All tickets default to this component until someone updates it.

  
was already fixed

   
website

things about the tahoe-lafs.org website (and sometimes this Trac instance, shared with 'dev-infrastructure')

  
wontfix

   
worksforme
No labels
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
Milestone
Clear milestone
No items
No milestone
undecided
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1916
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?