Page Comparison

...

...

...

• If

  I/O errors are recorded in the log if the Health Processor is actively scanning a

  drive

  disk 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

  disk 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

  disk.

• If you insert that drive

  Both recovery processes stop if a disk is inserted 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 recreated elsewhere. In time, the excess replicas or segments are deleted.

• If you insert a non-Swarm drive in a node,

  Swarm recognizes, formats, and mounts

  the drive

  a disk as a new volume if a non-Swarm disk is inserted in a node.

• If you insert a

  A Swarm-formatted

  drive

  disk continues to function as a volume without loss of data if inserted, 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 Swarm-formatted drive that was previously retired, the volume remains retired

  .

• A volume remains retired if a previously retired Swarm-formatted disk is inserted. No manual configuration or intervention is required.

• Messages display in logs and in the Swarm Admin Console to indicate

  that

  a

  drive

  disk was inserted or removed.

• If you are inserting multiple drives into the same server chassis, you need to wait

  Wait 2 minutes between

  drive

  disk insertions to

  ensure the

  guarantee new

  drives

  disks are evenly distributed across

  the

  multiple nodes

  that may be

  running on the chassis if inserting multiple disks into the same server chassis.