...
Note
...
Swarm requires control of all
...
volumes (disk.volumes = all
) to support hot plugging.
- If
I/O errors are recorded in the log if the Health Processor is actively scanning a
drivedisk when it is removed
, I/O errors are recorded in the log. These errors are expected and do not indicate a problem.
When a
drivedisk 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 werestored on that
drivedisk.
- If you insert that drive
Both recovery processes stop if a disk is inserted in the same node or
ina 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 werealready 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 drivea disk as a new volume if a non-Swarm disk is inserted in a node.
- If you insert a
A Swarm-formatted
drivedisk 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
thata
drivedisk was inserted or removed.
- If you are inserting multiple drives into the same server chassis, you need to wait
Wait 2 minutes between
drivedisk insertions to
ensure theguarantee new
drivesdisks are evenly distributed across
themultiple nodes
that may berunning on the chassis if inserting multiple disks into the same server chassis.
Infonote | |
---|---|
title | CautionWhen adding or relocating volumes to a node, ensure thatverify the node has enough RAM to handle them . If not, it might, else the node may be unable to mount some of the volumes. |
Infonote | |
---|---|
title | WarningDo not move Swarm drivesdisks between disk array controller types after they have beenare formatted by Swarm. Each controller reports available drivedisk space to Swarm that ismatched with the controller. For example, many controllers claim the last section of the drivedisk, reducing the total available space. If you switch your drives with another controller, theThe new controller may claim additional drivedisk space that isnot reported to Swarm, so Swarm may tryattempt to write data to non-existing space, generating I/O errors if disks are switch with another controller. |