Use the following set of Managing Configuration Settings to enforce your content integrity policy.

scsp.replicateOnWrite

This option allows an administrator to force a second replica of an object to be written to a different node before returning a success status to the client. If either write operation fails, the client receives an error status.

In the Swarm UI, it appears under the SCSP section of the Cluster Settings page:

See Configuring ROW Replicate On Write.

scsp.validateOnRead

This option allows an administrator to require validation of all content reads before returning a successful read completion.

In the Swarm UI, it appears under the SCSP section of the Cluster Settings page:

Although this option can be specified on a per-read basis, setting the value to 1 in the configuration file forces all reads to use validation.

During the read from the drive, the content hash is computed. If the hash is wrong, indicating logical drive corruption, the socket is closed before the last block is transmitted, forcing an error to the client.