3.5.1 Matrix Server Release Notes

PolyServe Release Notes 24

13597 Solaris 8 and Solaris 10 clients can experience failover delays

When a Virtual NFS Service fails over to another server, a Solaris

10 client using TCP-based NFS mounts can pause for 80 to 90

seconds before I/O resumes normally. This delay is caused by a

client-side NFS RPC bug and applies only to NFS RPC over TCP.

UDP-based mounts are not affected. The problem can be

resolved by applying the recommended Sun patches for Solaris

10.

A similar problem exists on Solaris 8; however, it is significantly

rarer in occurrence and is not fixed by Sunʹs currently

recommended patches for Solaris 8. Delays of up to four

minutes may be experienced. Again, only TCP-based mounts

are affected. On Solaris 8, these delays can often be concluded by

running a command such as df on the client from a different

user session.

Solaris 9 does not have either of these issues.

15172 Storage Summary does not update the “Exports” column

When a node is removed from a Virtual NFS Server, the number

of exports displayed on the Storage Summary should change

when the Summary is refreshed. However, the Storage

Summary continues to report the previous number of exports.

To cause the Storage Summary to update the “Exports” column,

open the Properties for any Export Group and then click OK.

15293 Clients may experience failures when mounting many

filesystems

Clients attempting to mount too many NFS filesystems in rapid

succession may see unexpected permission failures. These

failures are caused by exhaustion of a client resource

(“privileged” ports), and can be avoided by mounting NFS

filesystems less rapidly. In general, fewer than 100 mounts

should be attempted within a two-minute period. The precise

limit is dependent on how the client host Internet protocol stack

is implemented and how busy the client host has been recently.

Defect Description