Date: Mon, 14 Dec 1998 10:56:57 -0800 (PST) From: Chris Timmons <skynyrd@opus.cts.cwu.edu> To: Joel Ray Holveck <joelh@gnu.org> Cc: Mark Huizer <freebsd@xaa.iae.nl>, current@FreeBSD.ORG Subject: Re: ^@^@^@^@^@^@^@ (empty pages) in NFS served file. Message-ID: <Pine.BSF.3.96.981214105120.29247E-100000@opus.cts.cwu.edu> In-Reply-To: <864sqzmfgw.fsf@detlev.UUCP>
next in thread | previous in thread | raw e-mail | index | archive | help
I see something similar to this when mounting a filesystem on -current from a mid-july -stable using nfsv3. As soon as you fall back to nfsv2 things start working again. For example, mount a /usr/ports homed on a 2.2-stable system to a 3.0-current system and try building something big (eg. XFree86) on the -current system in the mounted filesystem. I'll have to try with -current vs. -current. Some of the -current NFS fixes may have been merged into 2.2 prior to 2.2.8 but I'm not sure and I doubt it. -Chris On 13 Dec 1998, Joel Ray Holveck wrote: > [moved to -current] > > > Hi! quite often I run into problems with NFS served files, containing a > > page of ^@^@^@^@^@^@^@'s instead of actual data (mostly noticed in > > textfiles). > > After checking on the server, it seems the data is valid there. Touch'ing > > it helps sometimes. > > Environment is 2x FreeBSD current, running nfsv3 over udp, on machines > > with softupdates enabled. > > Anyone having the same trouble?? > > Yes, on a small shared mail directory. I assumed that it was equally > corrupt on both client and server, but haven't verified that. All > file access to the file I'm monitoring has been from the same client, > with locking implements (not flock) to prevent simultanious writes. > Same setup as you describe, although I'm about to move the server to > -stable instead. > > Happy hacking, > joelh > > -- > Joel Ray Holveck - joelh@gnu.org > Fourth law of programming: > Anything that can go wrong wi > sendmail: segmentation violation - core dumped > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > 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.981214105120.29247E-100000>