Expanding a VDisk using the CLI
This task provides step-by-step
instructions for expanding a VDisk using the CLI.
VDisks can be expanded should it be required. However, if the VDisk contains
data that is being used, only AIX and Windows 2000 hosts can cope with a VDisk
being expanded. A VDisk that is not yet mapped to any hosts and hence does
not contain any customer data can be expanded at any time.
This feature can be used in two ways:
- To increase the capacity available on a particular VDisk that is already
mapped to a host. The procedure below outlines using this feature in this
way. The following matrix shows the supported platforms and requirements if
this feature is to be used:
Table 60. Supported platforms and requirements
| Platform |
Supported |
Requirement |
| AIX |
Yes |
AIX 5.2 onwards only |
| HP-UX |
No |
|
| Linux |
No |
|
| SUN Solaris |
No |
|
| Windows NT |
No |
|
| Windows 2000 |
Yes |
|
- To increase the size of a VDisk so that it matches the size of the source
or master VDisk and can be used in a FlashCopy mapping or Remote Copy relationship.
The following procedure does not need to be followed to use this feature in
this way. Ensure the target or auxiliary VDisk is not mapped to any host and
issue the following command:
svctask expandvdisksize
 | Note: You can determine the exact size of the source or master VDisk by
issuing the following command:
svcinfo lsvdisk -bytes <vdiskname>
|
 | Attention: This procedure allows you to expand a VDisk that is attached to
an AIX 5.2 host only. This procedure will deactivate the volume group to which
the VDisk belongs to for a short period of time. That is, I/O operations will
not be possible to any filesystem created in the volume group to which the
VDisk that is being expanded belongs. |
Steps
Perform the following steps to expand a VDisk that is mapped
to a AIX host:
-
Determine the VDisk you wish to expand and remember
its <vdiskname>.
- Determine the host that this VDisk is mapped to. You may need to follow
the procedure. If any of the hosts are running HP-UX, Linux, Solaris or Windows
NT, then you cannot continue.
- Determine the volume group that the VDisk belongs to (it is assumed you
know the VDisk to HDisk relationship as determined in step 1.
- Quiesce all I/O operations to all volumes that
belong to the volume group and sync the filesystems mounted on this volume
group.
- Issue the following command to find out the current type of the VDisk:
svcinfo lsvdisk <vdiskname>
If the VDisk has
a type of image it cannot be expanded. If the VDisk
has a type of sequential it will become striped when
you expand it.
- You must first deactivate the volume group to which this VDisk belongs
to. Issue the following command:
<AIX_HOST_PROMPT> varyoffvg <volume_group>
- Expand the VDisk by the required amount by issuing the following command:
svctask expandvdisksize -size <capacitytoexpandby>
-unit <unitsforexpansion> [ -mdisk <mdisklist> -fmtdisk ]
<vdiskname/ID>
- Re-activate the volume group so that the change in size is detected by
the HBA device driver. Issue the following command:
<AIX_HOST_PROMPT> varonvg <volume_group>
- Run the change volume group to notify the LVM that the size has changed.
Issue the following command:
chvg -g <volume_group>
- Expand the filesystem(s) that are mounted on this VDisk (or use the new
capacity as required).
- Restart I/O operations to the VDisk.
Steps
Perform the following steps to expand a VDisk that is mapped
to a Windows 2000 host:
- Ensure that you have run Windows Update and have applied all recommended
updates to your system prior to attempting to expand a VDisk that is mapped
to a Windows 2000 host.
 | Note: VDisks can be expanded under Windows
2000 concurrently with I/O operations. |
- Expand the VDisk by the required amount by issuing the following command:
svctask expandvdisksize -size <capacitytoexpandby> - unit <unitsforexpansion> [ -mdisk <mdisklist> -fmtdisk ] <vdiskname/ID>
- On the Windows Host, start the Computer Management application and open
the Disk Management window under the Storage branch.
Restart the Computer
Management application if it was opened prior to expanding the VDisk and the
disk.
- You will see the disk that you expanded now has some unallocated space
at the end of the disk.
If the disk is a windows basic disk you can create
a new primary or extended partition from the unallocated space.
If the
disk is a windows dynamic disk you can use the unallocated space to create
a new volume (simple, striped, mirrored etc) or add it to an existing volume.
Dynamic disks can be expanded without stopping IOs in most cases. However,
in some applications the operating system may report IO errors. When this
problem occurs, either of the following entries may be recorded in the System
event log:
Event Type: Information
Event Source: dmio
Event Category: None
Event ID: 31
Description:
dmio: Harddisk0 write error at block ######## due to
disk removal
Event Type: Information
Event Source: dmio
Event Category: None
Event ID: 34
Description:
dmio: Harddisk0 is re-online by PnP
 | Attention: This is a known problem
with Windows 2000 and is documented at the Microsoft knowledge base as article
Q327020. If either of these errors are seen, run Windows Update and apply
the recommended fixes to resolve the problem. |
Related topics