Date: Fri, 15 Jan 1999 10:04:00 +0000 (GMT) From: Bob Bishop <rb@gid.co.uk> To: Bjoern Fischer <bfischer@Techfak.Uni-Bielefeld.DE> Cc: Chris Timmons <skynyrd@opus.cts.cwu.edu>, freebsd-current@FreeBSD.ORG Subject: Re: NFS woes: getting worse? Message-ID: <Pine.BSF.3.96.990115094756.17318A-100000@seagoon> In-Reply-To: <19990115072732.A983@frolic.no-support.loc>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Fri, 15 Jan 1999, Bjoern Fischer wrote: > On Thu, Jan 14, 1999 at 08:03:46PM -0800, Chris Timmons wrote: > > > > I have duplicated on two pairs of machines a case whereby you have two > > -current machines as of ~20:00 UTC 1999/Jan/14 which cannot interoperate > > via NFS without corruption. > > > [...] > > 18034 bytes read by the NFS client, 19229 bytes read on the local system! > > > > The file shown in the kdump output above is "Makefile" (see path below), > > and we can see that it's true size is 19229. This is just one instance of > > the problem. > [...] > > Same problems here -- or even worse. > > Running -current on a NFS-server and several diskless clients > attached to it (I like the silence at my desk), I get truncated > files and NFS-writes with a lot of ^@^@^@^@^@ and some other > garbage in it. I'm seeing the same thing with src-cur.3700, ~10 Jan. Doing `make depend' for the kernel I get the ^@^@+crap towards the end of .depend, and it's completely repeatable. Guess I'll see what tcpdump has to say unless someone can suggest something more effective. The server is otherwise unloaded, so I guess load isn't a factor. FWIW, the client is a rather faster machine than the server and the link is 10Mb. -- Bob Bishop +44 118 977 4017 rb@gid.co.uk fax +44 118 989 4254 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.990115094756.17318A-100000>