Changes between Initial Version and Version 1 of Ticket #671, comment 26
- Timestamp:
- 2014-09-24T04:31:18Z (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #671, comment 26
initial v1 2 2 Looks like #1836 is intended to address the long delays in calculating exactly how much space the storage node is actually using. 3 3 4 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. 4 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.