3.1.2 Matrix Server RHEL4 Release Notes

PolyServe Matrix Server Release Notes 4

• Defect 12875. A flaw in mxregd’s recovery processing could cause it to

not finish, which would then cause dependent components of the

system to not function.

• Defect 12877. The perfservice logs grew too large and could eventually

fill the /var filesystem.

• Defect 12892. grpcommd needed to be able to shut down Matrix

Server if ClusterPulse was hung.

• Defect 12899. grpcommd crashed during a membership transition.

This problem occurred only under extreme circumstances.

• Defect 12966. An error-handling path had a bug that could cause a

machine to crash or filesystem operations to hang following an I/O

error.

• Defect 12967. A filesystem could generate so much I/O that other

important parts of the system could not run, causing a panic.

• Defect 13048. In a misconfigured non-symmetric network

configuration, PanPulse could spin and use all CPU resources trying

to discover and agree upon the network topology. (A non-symmetric

configuration is unsupported.)

• Defect 13055. An inconsistency existed between an assertion in a lockd

routine and the underlying return values from the filesystem. This

inconsistency could cause the system to crash.

• Defect 13062. If Matrix Server was unable to discover an FC switch

during device discovery (for example, because the switch was down),

the fencing information for that switch was deleted.

• Defect 13147. Sanpulse could exit while the product was starting

because ClusterPulse had not established interprocess communication

with it.

• Defect 13200. Matrix Server did not correctly detect that the IBM SDD

multipath driver was installed, resulting in misleading error

messages.

• Defect 13241. The mx matrix destroy command could cause SANPulse

to core dump.