HP StorageWorks Automated Storage Manager Release Notes (5697-0391, June 2010)

Issue: Extending storage space to the maximum allowed size fails and displays an error message.
After storage is created in ASM, a size range is displayed that indicates the minimum and maximum size that
the storage space can be extended (for example, 15MB - 272GB). When using the Allocate Space function to
extend storage to the displayed maximum space allowed, the operation fails and an error message is displayed.
Workaround: Enter a smaller value than the maximum size allowed that is displayed in the ASM user interface
until the operation is successful. This issue will be resolved in a future release.
Issue: Windows reports multiple instances of the Virtual Disk Service (VDS) provider failing.
These error messages are reported because the VDS Hardware Provider installed on HP Storage Servers has
stopped due to an internal error. When ASM discovers that VDS is not in a consistent state, VDS is automatically
stopped and its state is refreshed. As a result, this does not impact storage provisioning with ASM.
Workaround: These errors can be safely ignored. There is no effect on VDS functionality.
Issue: When performing storage tasks such as extending LUNs and deleteing LUNs using DiskRAID and ASM,
a VDS application error may be issued.
Workaround: This error can be safely ignored; there is no functionality impact to ASM.
Issue: Shared folders that have no file system quota assigned to them cause unexpected behavior in ASM.
The following behavior may be observed in the ASM user interface for shared folders that have no file system
quota:
1. The properties dialog for a shared folder that was created using ASM or a shared folder that was created
outside ASM but discovered by ASM includes a Warning Threshold tab. If the shared folder has no file
system quota assigned to it, the text on this tab is incorrect. The text should indicate that a file system
quota should be applied to the shared folder.
2. The Allocate space action will incorrectly display a size of 0 MB for the shared folder and continuing with
the Allocate space action will grow the volume by unexpected amounts.
3. If a file system previously existed (for example, when the shared folder was created with ASM) and is
removed, ASM will continue to display the original quota information.
Workaround: To resolve issues 1 and 2, applying a file system quota to the shared folder. To resolve issue 3,
select the Remove from view action for the shared folder in the ASM user interface.
Issue: When provisioning storage, ASM fails to grow the logical disk capacity to the requested capacity, even
though the ASM user interface indicates adequate capacity. This is an intermittent issue.
Workaround: Retry the operation after the discovery process is complete.
Issue: The ASM Grow/Extend Volume command fails intermittently.
The Grow/Extend Volume command sometimes returns a failure even though the operation completes successfully
and the volume capacity matches the requested size.
Workaround: Retry the operation after completing the Discovery process.
HP Automated Storage Manager 4.0 Release Notes 5