MSA 2040 SMU Reference Guide

Configuring a vdisk 57
If a disk in the vdisk fails, a dedicated spare is automatically used to reconstruct the vdisk. A fault-tolerant vdisk other
than RAID-6 becomes Critical when one disk fails. A RAID-6 vdisk becomes Degraded when one disk fails and
Critical when two disks fail. After the vdisk’s parity or mirror data is completely written to the spare, the vdisk returns
to fault-tolerant status. For RAID-50 vdisks, if more than one sub-vdisk becomes critical, reconstruction and use of
assigned spares occur in the order sub-vdisks are numbered.
To change a vdisk’s spares
1. In the Configuration View panel, right-click a vdisk and select Configuration > Manage Dedicated Spares. The
main panel shows information about the selected vdisk, its spares, and all disks in the system. Existing spares are
labeled SPARE.
In the Disk Sets table, the number of white slots in the Disks column of the SPARE row shows how many spares
you can add to the vdisk.
In the Graphical or Tabular view, only existing spares and suitable available disks are selectable.
2. Select spares to remove, disks to add as spares, or both. To add a spare, select its checkbox. To remove a spare,
clear its checkbox.
3. Click Modify Spares. If the task succeeds, the panel is updated to show which disks are now spares for the vdisk.
Changing a vdisk’s name
To change a vdisk’s name
1. In the Configuration View panel, right-click a vdisk and select Configuration > Modify Vdisk Name. The main
panel shows the vdisk’s name.
2. Enter a new name. A vdisk name is case sensitive; cannot already exist in the system; and cannot include a
comma, double quote, angle bracket, or backslash. The name you enter can have a maximum of 32 bytes.
3. Click Modify Name. The new name appears in the Configuration View panel.
Changing a vdisk’s owner
Each vdisk is owned by one of the controllers, A or B, known as the preferred owner. Typically, you should not need
to change vdisk ownership.
When a controller fails, the partner controller assumes temporary ownership of the failed controller’s vdisks and
resources, becoming the current owner. If the system uses a fault-tolerant cabling configuration, both controllers’ LUNs
are accessible through the partner.
CAUTION:
Before changing the owning controller for a vdisk, you must stop host I/O to the vdisk’s volumes.
Because a volume and its snap pool must be in vdisks owned by the same controller, if an ownership change will
cause volumes and their snap pools to be owned by different controllers, the volumes will not be able to access
their snap pools.
Changing the owner of a vdisk does not affect the mappings volumes in that vdisk.
To change a vdisk’s owner
1. In the Configuration View panel, right-click a vdisk and select Configuration > Modify Vdisk Owner. The main
panel shows the vdisk’s owner.
2. Select a new owner.
3. Click Modify Owner. A confirmation dialog appears.
4. Click Yes to continue; otherwise, click No. If you clicked Yes, a processing dialog appears. When processing is
complete a success dialog appears.
5. Click OK.