From owner-freebsd-current Sun Dec 13 21:59:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01625 for freebsd-current-outgoing; Sun, 13 Dec 1998 21:59:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (76-sweet.camalott.com [208.239.153.76]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01618 for ; Sun, 13 Dec 1998 21:59:24 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id XAA18140; Sun, 13 Dec 1998 23:59:13 -0600 (CST) (envelope-from joelh) To: Mark Huizer Cc: current@FreeBSD.ORG Subject: Re: ^@^@^@^@^@^@^@ (empty pages) in NFS served file. References: <19981213235615.A12800@ariel.xaa.iae.nl> From: Joel Ray Holveck Date: 13 Dec 1998 23:59:11 -0600 In-Reply-To: Mark Huizer's message of "Sun, 13 Dec 1998 23:56:15 +0100" Message-ID: <864sqzmfgw.fsf@detlev.UUCP> Lines: 26 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [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