[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:  code-mutable  |    Version:  1.9.2
   Resolution:                |   Keywords:  mutable publish heisenbug
Launchpad Bug:                |
------------------------------+---------------------------------------

Comment (by PRabahy):

 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.

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