3.1.2 Matrix Server RHEL4 Release Notes

PolyServe Matrix Server Release Notes 2

• Defect 12381. Multiple processes could hang while attempting to

perform write operations.

• Defect 12385. Down nodes were included in aggregate values on the

Performance Dashboard.

• Defect 12389. Unwanted failover/failback operations occurred when a

monitor became active after it had been down on all servers.

• Defect 12421. A race condition could prevent the perfservice process

from starting.

• Defect 12463. Shared memory objects used by the Performance

Dashboard infrastructure could in some situations collide with those

created by other applications in the system. This problem has been

fixed by handling shared memory key collisions more robustly.

• Defect 12472. When an attempt to create a snapshot timed out, the

filesystem could be left in a suspended state.

• Defect 12473.When the firmware on IBM BladeCenter Management

Modules was updated to version BRET82H, the IPMI fencing module

prematurely closed connections between the node and the

Management Module, causing fencing operations to fail.

• Defect 12491. Under certain failure conditions, SanPulse generated a

large volume of repetitive log information.

• Defect 12496. When EMC PowerPath was being used and network

accessibility to the FibreChannel switch was lost, it was possible for

the scld daemon to take a segmentation fault, thus causing Matrix

Server to shut down.

• Defect 12501. mxconfig crashed when trying to list the disks available

for membership partitions.

• Defect 12502 and 12875. A flaw existed in mxregd data store recovery.

When the problem was encountered, the recovery would fail, causing

Matrix Server components that rely on the mxregd data store to hang.

• Defect 12507. After a server was fenced, an alert stating that the server

should be rebooted did not always appear on the PolyServe

Management Console.