4.0.0 HP Polyserve Matrix Server Release Notes (T5392-96051, March 2010)

DescriptionIssue
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
lanman IRPStackSize is too small
After installing applications that use the IRP stack (such as some AntiVirus software), you may see
error messages indicating that the value of the lanman IRPStackSize parameter needs to be increased.
This problem has also been seen when upgrading Matrix Server from a release earlier than 3.4.
(Matrix Server uses an additional IRP stack in release 3.4 and later.)
The error messages are as follows:
Not enough server storage is available to process this command.
Not enough memory to complete transaction. Close some applications and
retry.
Event ID : 2011
Source : Srv
Description: The Server's configuration parameter "IRPStackSize" is too
small for the server
to use a local device. Please increase the value of this parameter.
The following Microsoft Knowledge Base article explains how to resolve this problem:
http://support.microsoft.com/?scid=kb;en-us;177078
It is recommended that the IRPStackSize be raised by increments of 1 until the error is resolved.
14219
Memory-mapped sparse files are not supported
Attempts to create a memory-mapped sparse file or to mark an existing memory-mapped file as
sparse will fail with a “Status not supported” error.
15437
Roles can allow users to run scripts as LocalSystem
A role granting create or modify rights for monitor or notification scripts allows the user to run the
scripts as LocalSystem, effectively allowing the user to be a machine local administrator. If security
is a concern, ensure that only machine local administrators are allowed to create or modify event
notification settings and monitors. (Monitors are included in the application, file-serving, and SQL
resources.)
16442
Matrix Server is not compatible with Microsoft Forefront Client Security product
Using the Forefront Client Security product on a Matrix Server node causes the node to bugcheck
in the PSFS filesystem. This issue occurs because of an incompatibility between the Matrix Server
PSFS filesystem and the Forefront Client Security product. We have reported this incompatibility to
Microsoft and are working to fix it.
16858
Removing the Microsoft SNMP service causes Matrix Server SNMP agent to fail
If the Microsoft SNMP service is uninstalled, the Matrix Server SNMP extension agent will fail to
send traps. This problem occurs because registry entries for the Matrix Server SNMP extension agent
are removed when the Microsoft SNMP service is uninstalled. Reinstalling the Microsoft SNMP
service does not restore the registry entries for the Matrix Server SNMP extension agent.
Workaround. The preferred workaround is to uninstall Matrix Server (saving the configuration) and
then reinstall it. If this is not possible, open Windows Explorer and go to \bin in the Matrix Server
installation directory, double-click on mxsnmp_add.reg, and then reboot.
17209
HP PolyServe Matrix Server release notes 11