4.1.0 HP Polyserve Matrix Server Release Notes (T5392-96068, October 2010)

DescriptionNumber
Add or Remove Programs appears to hang
On startup, Add or Remove Programs enumerates the contents of all top-level directories of mounted
volumes. When the root or top-level directories on PSFS filesystems contain large numbers of files,
Add or Remove Programs appears to hang during this step.
Workaround. Do not overpopulate the root directory and the top-level directories of PSFS filesystems
with large numbers of files. Instead, place the files in subdirectories.
12924
Filesystem is not recreated with previous options
The Recreate Filesystem window on the PolyServe Management Console contains an Options
button. If you recreate a filesystem and do not open the Options dialog, the filesystem will be
recreated with the default options instead of the options that were set when the filesystem was
originally created.
Workaround. When you recreate a filesystem, open and then close the Options dialog before
clicking OK on the Recreate Filesystem Window. The filesystem will then be recreated with its
original options.
13107
Shadow copy option is available for snapclones
When you create a snapclone on the Create Snapshot window, the option to “Share as Shadow
Copy of Shared Folder” is available; however, a shadow copy cannot be created from a snapclone
and the option is unused.
13275
Synchronized bookmarks do not work with secondary interface
If you are unable to connect to the matrix using the primary network interfaces on your servers
because of the network infrastructure or a firewall, the “Synchronize Server Bookmarks
Automatically” option should be disabled. If it is not disabled, bookmarks that contain addresses
on a secondary interface will be replaced with the unreachable primary interface.
13411
The Java client VM terminates when mx commands are run from a monitor script
Although not a fix for this issue, placing a .matrixrc file in the following folder may prevent the
crash.
C:\Documents and Settings\Default User\
13587
vssadmin cannot be used with snapshots
When snapshots are created through the PolyServe Management Console or the mx snapshot
command, they are created via the HP EVA array interface without the involvement of VSS
(Microsoft's Volume Shadowcopy Service). However, when you select the “Shadow Copies of
Shared Folders” checkbox, sufficient information must be created to inform VSS of the existence
of the snapshot so that it can be shared to CIFS clients.
These SCSF-enabled snapshots are visible in the output of vssadmin.exe list shadows and
they are identifiable by their all-zero GUIDS and other invalid information. These snapshots are
not real VSS snapshots, and cannot be deleted via the vssadmin command. They should generally
be managed with the PolyServe Management Console or the mx snapshot command instead.
13988
mx fs destroy partially destroys snapshots
Do not use the mx fs destroy command to remove a snapshot. If you attempt to delete a
snapshot with the mx fs destroy command, the snapshot filesystem will be removed but the
snapshot will remain on the array. You will then need to manually remove the snapshot LUNs from
the array. (After removing the LUNs, you will see disk import errors on the console for the LUNs
that were removed.)
If you need to delete a snapshot, either use the mx snapshot destroy command or locate the
snapshot on the PolyServe Management Console, right-click, and select Delete.
13996
10