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:
A volume is considered "stale" and its contents cannot be used unless an administrator specifically overrides this process if disconnected from the cluster for more than 2 weeks.
A node and all of its volumes are considered stale and cannot be used if it is shut down for more than 2 weeks.
The "stale" status is triggered by a service gap of 2 weeks, which is the default value for the disk.obsoleteTimeout setting.
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)
Reformatting volumes (recommended)
Reformatting the volume allows it to be filled by the health processor (HP) in an orderly fashion. Performing this prevents creating excessive work for the health processor and prevents generating trapped space needed to be reclaimed.
snmpset -v2c -c ourpwdofchoicehere -m ./CARINGO-MIB.txt:./CARINGO-CASTOR-MIB.txt 192.168.99.100 castorFormatStaleVolumeAction s "/dev/sda"
Important
The volume's encryption status is always retained on return to service; physical removal from Swarm is required to change it.
Remounting volumes
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.
Note
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.
snmpset -v2c -c ourpwdofchoicehere -m ./CARINGO-MIB.txt:./CARINGO-CASTOR-MIB.txt 192.168.99.100 castorRemountStaleVolumeAction s "/dev/sda"