HP AK373A - StorageWorks All-in-One Storage System 1200r 5.4TB SAS Model NAS Server Release Notes page 6

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: Replication operation in ASM may fail on non-English systems.
A non-ASCII path may be created by ASM on non-English systems; however, HP StorageWorks Storage
Mirroring does not properly handle non-ASCII paths. As the result, replication may fail during the Replicate
component subtask.
Workaround: Change the system account language to English:
1. Log on to the storage system with the local Administrator account.
2. Change the System and Administrator account to English:
a. In Control Panel, double-click Region and Language Options.
b. On the Formats tab, select English (United States) under Current format.
c. On the Location tab, select United States under Current location.
d. On the Keyboards and Languages tab, select English under Choose a display language.
e. On the Administrative tab, click Copy to reserved accounts.
f. Check System accounts (local system, local service, and network service), and then click OK.
g. On the Administrative tab, click OK.
h. Restart the storage system.
3. Log on to the storage system with the local Administrator account.
4. Change the Administrator account back to your preferred language:
a. In Control Panel, double-click Region and Language Options.
b. Select your preferred options on each tab, but do not copy the settings to System account.
c. Log off and then log back into the storage system.
Issue: When updating older versions of ASM to ASM version 3.9.0, some existing virtual libraries are moved
to Remote Virtual Libraries area of ASM.
Workaround: Not applicable. There is no impact to data or applications.
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.
Issue: NFS share folder creation fails when the NFS share folder name contains spaces.
Spaces are not allowed in NFS share names. If a space is included in an NFS share folder name, it is
automatically replaced by Windows with the underscore symbol (_). If an NFS share folder exists with the
same name (including the underscore symbol), a Windows prompt appears requesting a new NFS share
folder name. ASM, however, cannot check for or replace spaces in NFS share folder names during task
execution because CIFS share names do allow spaces.
Workaround: Do not include spaces in NFS share names. This issue will be addressed in a future release.
6