tktk@physics.att.com (Terry Kovacs) (07/21/89)
In Volume 8 : Issue 74 Peter Jensen comments: > We're > still waiting to get an NFS problem fixed - Is anyone else having problems > with their remote files getting corrupted (some bytes being replaced by > garbage or nulls)? Yes, we have seen this problem but really aren't sure that it is associated with NFS or the particular device that the data was being written to (or some nasty interpay between the two). I heard a explaination that a possible cause for NFS problems was that NFS turns off check sums on the UDP packets it sends. I verified that this is indeed the case by looking at the packet headers. I'd like to turn check summing on to see if it helps. Does anyone know how to do this? Terry Kovacs
carnone@homxc.att.com (Christopher Arnone) (07/03/90)
I recently had to add a diskless Sun 3/80 client to a Sun 3/80 standalone. I followed the documentation describing how to convert my standalone system to an NFS server. Everything went according to plan, except that when I used the "setup_client" command, I had to put the swap space for the client in "/usr/swap" instead of "/export/swap". All went well however. The client boots up just fine, but occasionally reports "NFS write error type 13" on the server during network transactions. In additon, "sundiag" on the client reports seek errors on FD 0. "Sundiag" on the server shows both drives pass diagnostics OK. Basically, I'm lost at this point. Can anyone offer some insight?? I can't believe that the disks on my server (was a standalone) are bad because they never exhibited any problems up to now. Please respond via email. Thanks in advance........... Chris Arnone attbl!homxc!carnone