HP StorageWorks Automated Storage Manager 4.1 Release Notes (5697-0622, November 2010)

Issue: When performing storage tasks such as extending LUNs and deleting 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: ASM may fail to run the correct operations on storage recently modified with non-ASM tools
If you use a non-ASM tool (such as the Array Configuration Utility, for example) to modify storage settings,
you must allow ASM time to recognize those new settings during the discovery process. If you attempt to
perform storage operations before the discovery process is complete, ASM will erroneously attempt to perform
storage operations such as growing non-existent logical disks.
Workaround: When modifying storage settings outside of ASM, allow enough time for the ASM discovery
process to recognize those new storage settings before performing any other ASM operations.
Issue: When attempting to provision storage on ASM, an error message appears
When attempting to provision storage, an error message indicating that “ no storage could be found or created
to satisfy the request” may be issued. This error can appear when attempting to provision storage across
multiple disk types.
Workaround: Virtual arrays that span multiple disk types cannot be created. When provisioning storage, the
maximum amount of space you can allocate is limited by the largest amount of space available for a single
disk type. You cannot completely utilize the space on all of the disks if the disks are of different types.
Data Protector Express
This section describes issues related to Data Protector Express
6