This is a bug. I received a preliminary patch for it as part of a call I logged
to Compaq (log #C000602-3573), and the patch appears to solve the problem.
Unfortunately, the patch will *NOT* be part of the first v5.0A patch kit.
At 12:18 PM 6/2/2000 -0400, you wrote:
>I apologize for the repost - my mailer messed up the subject line. :(
>
>After upgrading my AS1000A from Tru64 5.0 to v5.0A, the machine is now
>suddenly suffering from serious NFS problems.
>
>This machine is an NFS client to both a DS20 running Tru64 4.0F and
>and Auspex fileserver (SunOS 4.1.4). On *BOTH* these servers, NFS
>writes from the AS1000A fail with the (NFS server-side syslog) error
>
> 'xdrmbuf_getmbuf failed'
>
>On the client side, an I/O error is logged:
>
> 190% df /home/faxpds20/harbaugh
> Filesystem 512-blocks Used Available Capacity Mounted on
> faxpds20:/users 15360000 1615382 13744618 11% /home/faxpds20
> 191% df .
> Filesystem 512-blocks Used Available Capacity Mounted on
> /dev/disk/dsk14g 2078892 12968 1858034 1% /var/tmp
> 192% mount | grep ds20
> faxpds20:/users on /home/faxpds20 type nfs (v3, rw, nosuid, nodev, udp, soft, intr)
> 193% cp glib-1.2.7.tar.gz /home/faxpds20/harbaugh
> NFS3 RFS3_WRITE failed for server faxpds20 : RPC: Server can't decode arguments
> cp: /home/faxpds20/harbaugh/glib-1.2.7.tar.gz: I/O error
>
>In the example above, the NFS server is (of course) the DS20 mentioned above.
>The *identical* behavior is observed when transferring files to the Auspex.
>
>Does anyone know how to fix this? What has changed between Tru64 5.0 and 5.0A
>that would cause this?
>
>Thanks
>
>Toni
>
>-----------------------------------------------------------------------
>Toni Harbaugh-Blackford harbaugh_at_nciaxp.ncifcrf.gov
>AlphaServer 8400 System Administrator
>SAIC/NCI Frederick Advanced Biomedical Computing Center
>
Received on Thu Jul 13 2000 - 11:16:23 NZST