From owner-freebsd-current Tue Apr 21 04:46:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA21918 for freebsd-current-outgoing; Tue, 21 Apr 1998 04:46:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA21895 for ; Tue, 21 Apr 1998 11:46:25 GMT (envelope-from evanc@synapse.net) Received: (qmail 15971 invoked from network); 21 Apr 1998 11:46:24 -0000 Received: from cpu1970.adsl.bellglobal.com (HELO cello) (206.47.37.201) by conductor.synapse.net with SMTP; 21 Apr 1998 11:46:24 -0000 Message-ID: <008401bd6d1b$1c5ddd20$c9252fce@cello.synapse.net> From: "Evan Champion" To: , "Stephen McKay" Cc: Subject: Re: NFS corruption Date: Tue, 21 Apr 1998 07:46:23 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I ran 'make -j2 buildworld' and several hours later observed unusual error >messages complaining about garbage in .depend files. Many .depend files >were affected. Each .depend file was broken similarly. They would start >normally, then the corruption would start on a page boundary (multiple of >0x1000), but *not* extend as far as the next page boundary. The corruption >was either C source, or C preprocessor output overwriting the normal contents. I have similar results, on 2.2.6-STABLE. I have also in the past seen the .depend's full of nulls. The only major difference is that my entire .depend is preprocessor output, and not just a page-worth. Mounting with nfsv2 seemed to have fixed that problem, but then I ran in to dead .nfs* files being left around, which caused grief elsewhere. I haven't been able to build over NFS since at least March, possibly even January or February. Evan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message