[tahoe-lafs-trac-stream] [tahoe-lafs] #1943: storage servers should report if the filesystem containing shares has been unmounted

[tahoe-lafs]

#1943: storage servers should report if the filesystem containing shares has been
unmounted
------------------------------+--------------------------------------
     Reporter:  daira         |      Owner:
         Type:  defect        |     Status:  new
     Priority:  normal        |  Milestone:  undecided
    Component:  code-storage  |    Version:  1.9.2
   Resolution:                |   Keywords:  usability removable-disk
Launchpad Bug:                |
------------------------------+--------------------------------------

Comment (by gdt):

 I wouldn't call it a "UI" fix (tahoe has an odd culture of expecting a
 filesystem to be used by a human instead of by a computer (WUI)).

 I'd call this ticket a specific case of the more general issue of fault
 handling and monitoring.  An unmounted fs is not so different from one
 with bad permissions.  The point is probably that if the server thinks it
 can't store shares (because it did some access(2)-like check, or because
 it tried and failed), then it needs to report that in the introducer
 protocol.  It can still be online but without read access to shares it
 should have, or without write access, and this is useful information both
 to humans and programmatic clients.

 It makes my head hurt to think about the proper behavior of doing repair
 when there is a server that says it has shares but can't get to them right
 now.  I'd say this should be treated the same as the server not being
 present, for starters.

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