The storage cluster is designed to automatically adapt when a volume (hard drive) or node fails for any reason. Swarm checks every storage cluster volume during the node startup procedure, and it tracks any gaps in service that trigger a status change:
...
Force a volume remount by modifying the disk.volumes setting and adding the :k (keep) policy option. Return them to service dynamically (either remounting or reformatting) using SNMP. (v9.3)
...
It is rarely desirable to remount a volume that has stale content. The volume's missing content is recovered by this time and the cluster has its full complement of replicas of the cluster's content. Adding extra replicas creates work for the health processor to sift through the replicas, cleaning up redundant and obsolete copies. This cleanup creates trapped space in the cluster that take several HP cycles to reclaim.
| Info |
|---|
NoteBe aware content that was Content explicitly deleted by clients can be inadvertently resurrected when forcing a stale volume back in to service. This is not a problem for content automatically deleted by lifepoint policies because the obsolete content is discovered and deleted by the Swarm health processor. |
...