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

DescriptionNumber
mx check command incorrectly reports that fencing is not configured
This situation can occur when mx commands are used to configure the cluster, including the fencing
method. The fencing configuration file, fence.conf, is included in the files exported to the other
nodes; however, it might not exist on the node where the configuration was created. The mx
check command reports the error because it cannot find the fence.conf file. The missing
fence.conf file will not cause any operational issues on the node.
Workaround. Run the mx check command again on another node in the cluster to verify the
fencing configuration. (Include the ––matrix <hostname> option in the command to specify
the node where you want to run the command.)
20987
Windows Resource Kit subinacl.exe tool causes errors
Errors occur when the Windows Resource Kit subinacl.exe tool in used in a monitor script.
This tool should be not included in any monitor scripts.
21130
An error event is logged when starting perfmon.exe or a related application
On 64-bit systems, when either the \windows\syswow64\perfmon.exe command is invoked
or a 32-bit application that uses the perflib API (such as the Matrix Server gmond application) is
started, the Windows performance monitoring subsystem loads all of the registered Perfmon
extensions. If a registered Perfmon extension does not have a corresponding 32-bit extension dll
in an equivalent location, say in Program Files(x86), an error Event will be logged in the event
log.
Workaround. To avoid the event log entry, add the [Disable Performance Counters = 2] DWORD
registry value to this registry key:
HKLM\System\CCS\Services\<service>\Performance
Matrix Server does this for its Perfmon extension (mxperfext), but other vendors may not, resulting
in the event log messages.
21440
Shutdown is slow when machine is under heavy filesystem load
When shutting down a machine while it's running a very heavy filesystem load, the shutdown may
take a long time, and sometimes the machine may eventually crash.
22305
A bugcheck can occur in RDBSS.SYS
An issue exists with older versions of cygwin, and possibly other older applications, that involves
Microsoft recycling a deprecated file create flag. Windows 2008 interprets this flag differently
than the older code did, and this new interpretation causes a bugcheck in RDBSS.SYS. HP
recommends that, if you use older versions of cygwin, you update to version 1.7 (released
December 2009) and/or install the patch that Microsoft is releasing for RDBSS.SYS. This patch
is in Knowledge Base (KB) article 976266. This KB article can be found by going to
MSDN.microsoft.com, clicking on the support tab, and entering the KB number into the search
box (there are other valid ways to get to the KB as well). Note that this KB and associated patch
may not be released by Microsoft until after HP PolyServe Matrix Server 4.0.0 ships from HP.
27898
Hyper-V guest OS does not start after running psfscheck
After shutting down the guest OS and running psfscheck on the filesystem, the following error
appears when you attempt to restart the guest OS.
Failed to change the state
Workaround. Wait a few minutes for the locks to clear and then restart the guest OS manually.
27970
mx quota setgroup command does not work
When the mx quota setgroup command is issued, the following error appears:
unable to resolve name Administrators
28193
HP PolyServe Matrix Server 4.1.0 release notes 13