...
...
...
...
| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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)
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.
With support tools updated, you can use swarmctl from your support tools directory to return a disk to service by reformatting the disk. This command does not work when run from CentOS 6 (like the CSN) but will work from any SCS, Content Gateway, or Elasticsearch node. You can specify the disk or, if left blank, it will reformat all stale disks on that node.
| Code Block |
|---|
./swarmctl -d 192.168.4. |
...
173 -F /dev/sda -p "admin:datacore" |
On any CentOS 6 based system, use SNMP for this procedure using the MIBs in our support tools directory using the read/write SNMP string as shown here. In this case, the MIBs are present in the current directory.
...
| Info |
|---|
ImportantThe volume's encryption status (Configuring Encryption at Rest) 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.
With support tools updated, you can use swarmctl from your support tools directory to return a disk to service by re-mounting the disk. This command does not work when run from CentOS 6 (like the CSN) but will work from any SCS, Content Gateway, or Elasticsearch node. You can specify the disk or, if left blank, it will remount all stale disks on that node.
...