3.5.1 Matrix Server Release Notes

PolyServe Release Notes 20

8808 Linux NFS client may pause uninterruptedly

NFS client applications that use blocking file locks (via fcntl())

will sometimes pause uninterruptedly for 30 seconds and then

(if they are not killed in the meantime) resume running

normally. This problem is caused by a bug in the Linux NFS

client.

Workaround. PolyServe has provided a version of the SLES9

and RHEL4 NFS clients with this problem fixed. It is licensed

under the GPL and available from PolyServe Customer Support.

8813 Clients may fail a blocked lock request

NFS client implementations based on Linux 2.4, Linux 2.6, and

potentially other operating systems and releases, may fail a

blocked lock request when the server recovers after a failover.

The lock failure is exposed by the NFS client to applications. A

more robust client implementation would reissue the pending

lock request after reclaiming any previously granted locks.

9041 --probeseverity value must be lower case

The value of the --probeseverity option to the exportgroup

command must be specified in lower-case letters. The command

does not report an error if upper-case letters are typed; however,

the option is set to the default value.

9081 File locks cannot be acquired when Matrix Server is not

running

When Matrix Server is installed, the NSM (network status

monitor) support is provided by /opt/polyserve/sbin/vstatd,

which replaces the traditional /usr/sbin/rpc.statd. vstatd is

cluster-aware and requires membership in an active cluster to

run. File locks can not be acquired over NFS while NSM support

is unavailable; lock requests will be rejected with ENOLCK.

Defect Description