[tahoe-lafs-trac-stream] [tahoe-lafs] #1916: Folder healthy, but still get 410 Gone

[tahoe-lafs]

#1916: Folder healthy, but still get 410 Gone
---------------------+----------------------------
 Reporter:  PRabahy  |          Owner:  davidsarah
     Type:  defect   |         Status:  new
 Priority:  normal   |      Milestone:  undecided
Component:  unknown  |        Version:  1.9.2
 Keywords:           |  Launchpad Bug:
---------------------+----------------------------
 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 pu
 blic:
 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 Untrusted Stores.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 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.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1916>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage