3.1.2 Matrix Server SLES9 Release Notes

PolyServe Matrix Server Release Notes 8

• Defect 11281. mxconfig could create more than one UI connection to

ClusterPulse, causing the Management Console to crash.

• Defect 11325. It was sometimes necessary to expand the top-level

Matrix element on the Management Console in order to see matrix

entities such as filesystems.

• Defect 11420. Problems with message-queue handling could cause a

temporary slowdown of Matrix Server administrative operations or

could cause Matrix Server to shut down on a server.

• Defect 11431. Snapshots occasionally did not appear on the

Management Console.

• Defect 11446. If Matrix Server was started simultaneously on all

servers in a matrix and one of the servers could not be imported into

the matrix, virtual host services on the matrix would not be started.

• Defect 11488. Removing a backup interface from a virtual host could

cause the Management Console to crash.

• Defect 11525. The mx service status --primary and --backup

arguments did not report the correct information.

• Defect 11553. The Free Local Disk Space test provided with the

mxcheck command did not calculate free space correctly in all

configurations.

• Defect 11563. The psfsck --rebuildtree option could fail.

• Defect 11577. The Create Volume button was enabled on clusters that

were not licensed for dynamic volumes.

• Defect 11583. The Add button on the “Add Quota” dialog was

disabled when a user or group was deselected.

• Defect 11592. psfsck did not detect certain instances of corruption in

directories.

• Defect 11709. Extremely heavy loads on a server coupled with starting

or stopping Matrix Server on another server could result in a

filesystem being paused for a long period.