From owner-freebsd-questions Thu Mar 14 21:11:51 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA00425 for questions-outgoing; Thu, 14 Mar 1996 21:11:51 -0800 (PST) Received: from paloalto.access.hp.com (daemon@paloalto.access.hp.com [15.254.56.2]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA00419 for ; Thu, 14 Mar 1996 21:11:49 -0800 (PST) Received: from fakir.india.hp.com by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA170966698; Thu, 14 Mar 1996 21:11:44 -0800 Received: from localhost by fakir.india.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA168676974; Fri, 15 Mar 1996 10:46:14 +0530 Message-Id: <199603150516.AA168676974@fakir.india.hp.com> To: questions@freebsd.org Subject: NFS corruptions / FreeBSD 2.1 Date: Fri, 15 Mar 1996 10:46:13 +0530 From: A JOSEPH KOSHY Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Folks, The setup here: I have a FreeBSD machine mounting a 1 GB disk from a HP workstation. FreeBSD 2.1.0-RELEASE/16MB/500MB-IDE/HP PC Lan+ card HP9000/712 running HPUX9.0 offering a 1 GB disk read/write over NFS. The problem: when doing a sequence of NFS writes to the disk sometimes reads of other files from the same NFS mounted disk get corrupted data. The scenario is a follows: a) I'm writing a file say "file-a" to the NFS mounted disk b) while this is going on I read "file-b" from the same disk I occasionally see (a) NULLS and (b) data for "file-a" in "file-b". I've verified that the data that is actually written to remote disk for "file-b" is correct. Flushing the FS cache by reading/writing lots of data sometimes causes the correct data for "file-b" to be read off the NFS mounted disk. Small files are never corrupted. Stopping NFS writes to the remote disk causes the problem to go away. I did see a posting in the questions-archives about a similar-sounding corruption using NFS reads and writes (look for the subject "File Corruption Problem"). The rest of the system has been working fine till now; so I suspect its something to do with NFS. Is there anything I can do to work around this? Koshy