This task provides step-by-step instructions about how to create a MDisk group.
| Attention: If you add a MDisk to a MDisk group as a managed disk, any data on the MDisk will be lost. If you want to keep the data on a MDisk (for example because you want to want to import storage that was previously not managed by a SAN Volume Controller) then you should create image mode VDisks instead. |
Assume that the cluster has been setup and that a back-end controller has been configured to present some new storage to the SAN Volume Controller.
Before creating managed disk groups consider how you are going to use your storage. The SAN Volume Controller allows you to create up to 128 managed disks groups and to add up to 128 MDisks to an MDisk group. Consider the following factors when deciding how many managed disk groups to create:
Even with the best planning, circumstances may change and you may wish to reconfigure your managed disk groups after they have been created. The data migration facilities provided by the SAN Volume Controller enable you to move data without disrupting I/O.
Choosing a managed disk group extent size: You must specify the extent size when you create a new MDisk group. You cannot change the extent size later; it must remain constant throughout the lifetime of the MDisk group. MDisk groups may have different extent sizes however this will place restrictions on the use of data migration. The choice of extent size affects the total amount of storage that can be managed by a SAN Volume Controller Cluster. Table 103 shows the maximum amount of storage that can be managed by a cluster for each extent size. Because the SAN Volume Controller allocates a whole number of extents to each virtual disk that is created, using a larger extent size may increase the amount of wasted storage at the end of each virtual disk. Larger extent sizes also reduces the ability of the SAN Volume Controller to distribute sequential I/O workloads across many managed disks and hence may reduce the performance benefits of virtualization.
| Extent Size | Maximum storage capacity of cluster |
| 16MB | 64TB |
| 32MB | 128TB |
| 64MB | 256TB |
| 128MB | 512TB |
| 256MB | 1PB |
| 512MB | 2PB |
| Attention: You can specify different extent sizes for different managed disk groups, however you will not be able to migrate virtual disks between managed disk groups with different extent sizes. Therefore if possible create all your managed disk groups with the same extent size. |
Perform the following steps to create a MDisk group:
In our hypothetical scenario, the command to create a MDisk group is:
svctask mkmdiskgrp -name maindiskgroup -ext 32 -mdisk mdsk0:mdsk1:mdsk2:mdsk3
This command will create a MDisk group called maindiskgroup. The extent size used within this group will be 32 MB, and there are four MDisks mdsk0, mdsk1, mdsk2, mdsk3 added to the group.
In our hypothetical scenario, the command to create a second MDisk group is:
| Note: In this example we will create a second MDisk group first and add MDisks later. |
svctask mkmdiskgrp -name bkpmdiskgroup -ext 32
This command will create a MDisk group called bkpmdiskgroup. The extent size used within this group will be 32 MB.
To add MDisks to the MDisk group, issue the svctask addmdisk command. In our hypothetical scenario, the command to add MDisks to the MDisk group is:
svctask addmdisk -mdisk mdsk4:mdsk5:mdsk6:mdsk7 bkpdiskgroup
This command will add four MDisks mdsk4, mdsk5, mdsk6, mdsk7 to the MDisk group called bkpdiskgroup.