Child pages
  • How Netmail Store Responds to Drive Changes
Skip to end of metadata
Go to start of metadata


To support hot plugging, Netmail Store requires control of all of the volumes (disk.volumes = all).

  • If the Health Processor is actively scanning a drive when it is removed, I/O errors are recorded in the log. These errors are expected and do not indicate a problem.
  • When a drive is removed, volume recovery (FVR) and erasure coding recovery (ECR) are both triggered, which includes creating new replicas or erasure set segments for objects that were stored on that drive.
  • If you insert that drive in the same node or in a different node in the cluster, both recovery processes stop. There is a temporary state of over-replication because the returned volume has replicas or segments that were already re-created elsewhere. In time, the excess replicas or segments are deleted.
  • If you insert a non-Netmail Store in a node, Netmail Store recognizes, formats, and mounts the drive as a new volume.
  • If you insert a Netmail Store-formatted drive, either into the same node or into a different node, it continues to function as a volume without loss of data.
  • If you insert a Netmail Store-formatted drive that was previously retired, the volume remains retired. No manual configuration or intervention is required.
  • Messages display in logs and in the Netmail Store Admin Console to indicate that a drive was inserted or removed.
  • If you are inserting multiple drives into the same server chassis, you need to wait 1 minute between drive insertions to ensure the new drives are evenly distributed across the multiple nodes that may be running on the chassis.

Warning: When adding volumes to a node (either new or those from another machine), ensure that the node is configured with sufficient RAM to handle the additional storage. If a new node is not configured with enough RAM, the node might be unable to mount some of the volumes.

Do not move Netmail Store disks between disk array controller types after they have been formatted by Netmail Store. Each controller reports available disk space to Netmail Store that is matched with the controller. For example, many controllers claim the last section of the disk, reducing the total available space. If you switch your disks with another controller, the new controller may claim additional disk space that is not reported to Netmail Store, so Netmail Store may try to write data to non-existing space, generating I/O errors.

  • No labels