A is correct.
If a disk experiences sustained high latencies or congestion, vSAN considers the device as a dying disk, and evacuates data from the disk. vSAN handles the dying disk by evacuating or rebuilding data. No user action is required, unless the cluster lacks resources or has inaccessible objects.
A is right.
Dying Disk Handling monitors the performance of each storage device.
If a device experiences sustained high latencies or congestion, vSAN first isolates the device and considers the device a dying disk and then evacuates data from the disk.
Action taken by vSAN for the data on these disks or diskgroups depends on the configured policy and compliance state of objects that have their components on these disks or diskgroups:
• If a component on the unhealthy disk or diskgroup belongs to an object that can tolerate the failure of this disk or diskgroup, then vSAN immediately marks that component as absent to avoid any impact on the performance of writes to that object.
• If a component on the dying disk or diskgroup is required to maintain availability or quorum of a vSAN object, evacuation is triggered immediately.
No user action is required unless the cluster lacks resources or has inaccessible objects.
Taken from vSAN 6.7 Deploy and Manage Lecture Manual - About Dying Disk Handling section
A:
Dying Disk Handling monitors the performance of each storage device.
If a device experiences sustained high latencies or congestion, vSAN first isolates the device and
considers the device a dying disk and then evacuates data from the disk.
Action taken by vSAN for the data on these disks or diskgroups depends on the configured policy
and compliance state of objects that have their components on these disks or diskgroups:
• If a component on the unhealthy disk or diskgroup belongs to an object that can tolerate the
failure of this disk or diskgroup, then vSAN immediately marks that component as absent to
avoid any impact on the performance of writes to that object.
• If a component on the dying disk or diskgroup is required to maintain availability or quorum of
a vSAN object, evacuation is triggered immediately.
No user action is required unless the cluster lacks resources or has inaccessible objects.
I think A is correct.
Reason :vSAN applies a best effort procedure to evacuate all the “active” components from a “dying” disk but this process may fail if there are not enough resources in the cluster or if the components belong to inaccessible objects.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
hsezer
3 years, 2 months agoLazylinux
3 years, 6 months agodiegof1
4 years, 5 months agoCaptain_Chaos
4 years, 8 months agojasonv
4 years, 11 months agoAdy_14
5 years agoDenZn
5 years ago