[tahoe-lafs-trac-stream] [Tahoe-LAFS] #671: bring back sizelimit (i.e. max consumed, not min free)

[Tahoe-LAFS]

#671: bring back sizelimit (i.e. max consumed, not min free)
------------------------------+--------------------------------------------
     Reporter:  zooko         |      Owner:  markberger
         Type:  defect        |     Status:  new
     Priority:  major         |  Milestone:  1.12.0
    Component:  code-         |    Version:  1.3.0
  nodeadmin                   |   Keywords:  usability statistics sftp docs
   Resolution:                |
Launchpad Bug:                |
------------------------------+--------------------------------------------

Comment (by zooko):

 Replying to [comment:26 Lcstyle]:
 > Looks like #1836 is intended to address the long delays in calculating
 exactly how much space the storage node is actually using.

 Yes. And there is a good patch for #1836, but it isn't merged into trunk
 yet.

 > As far as what happens if a node originally given a limit of for example
 1TB and actually grows to this size, and afterwards an admin seeks to
 reduce the limit to 500GB, there should be some functionality that allows
 shares to be transferred or copied to other servers to accommodate the
 storage node's request to downsize or shrink.  It might take time to
 shrink the node, but at least it would provide the capability of a
 graceful way of resolving the issue.  I don't know if such functionality
 (or a FR for this functionality) already exists.

 There is another ticket about that, #864.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/671#comment:27>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage