HP Clustered FileSystem3.6.1 for Windows release notes (T4422-96003, September 2008)

Issue
20987
21 130
21440
22305
Description
mx chec k command incorrectly repor ts that fencing is not congured
This situation can occur when mx commands are used to congure the cluster,
including the fencing method. The fencing conguration le, fence.conf,is
included in the les exported to the other nodes; however, it might not exist on
thenodewhere theconguration was created. The mx check command reports
theerror becauseitcannot nd the fence.conf le. The m issing fence.conf
le 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 conguration. (Include the ––matrix <hostname> option
in
the command to specify the node where you want to run the command.)
Windows Reso
urce Kit subinacl.exe tool causes errors
Errors occur
when the Windows Resource Kit subinacl.exe tool in used in a
monitor scri
pt. This tool should b e not included in any monitor scripts.
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 perib API (such as the
HP Clustered File System 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 loc ation, 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 valuetothisregistrykey:
HKLM\System\CCS\Services\<service>\Performance
HP Clustered File System does this for its Perfmon extension (mxperfext ), but
other
vendors may not, resulting in the event log messages.
Shutdown is slow when machine is under heavy lesystem load
When shutting down a machine while it’s running a very heavy lesystem load, the
shutdown may take a long time, and sometimes the machine may eventually crash.
20