From owner-freebsd-current Mon Dec 14 10:57:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25910 for freebsd-current-outgoing; Mon, 14 Dec 1998 10:57:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25905 for ; Mon, 14 Dec 1998 10:57:16 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id KAA03514; Mon, 14 Dec 1998 10:56:58 -0800 (PST) Date: Mon, 14 Dec 1998 10:56:57 -0800 (PST) From: Chris Timmons To: Joel Ray Holveck cc: Mark Huizer , current@FreeBSD.ORG Subject: Re: ^@^@^@^@^@^@^@ (empty pages) in NFS served file. In-Reply-To: <864sqzmfgw.fsf@detlev.UUCP> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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