From owner-freebsd-bugs Thu Aug 13 11:24:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12762 for freebsd-bugs-outgoing; Thu, 13 Aug 1998 11:24:50 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from flea.best.net (flea.best.net [206.184.139.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12744; Thu, 13 Aug 1998 11:24:40 -0700 (PDT) (envelope-from dillon@flea.best.net) Received: (from dillon@localhost) by flea.best.net (8.9.0/8.9.0/best.fl) id LAA02830; Thu, 13 Aug 1998 11:24:11 -0700 (PDT) Date: Thu, 13 Aug 1998 11:24:11 -0700 (PDT) From: Matt Dillon Message-Id: <199808131824.LAA02830@flea.best.net> To: Mika Nystroem Cc: Peter Hawkins , mika@varese.cs.caltech.edu, freebsd-bugs@FreeBSD.ORG Subject: Re: kern/7596: serious data integrity problem when reading WHILE writing NFSv3 client-end Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org :Peter Hawkins writes: :>See also PR 7418 - the plot thickens... :> : :Hmm, this is very curious. You don't think the page boundary :business could have to do with stdio buffering (or some other :mechanism for delaying writes at the page boundaries)? : :I've managed to whittle down my test case to the following: :... : : :The random stuff is actually unnecessary, but it shows that the :problem is not page-boundary-related. The sine business is just :a delay loop, and is necessary. If the code looks a bit weird, :it's because it's "emulating" the I/O behavior of a version of :SPICE that exhibits the same problem. Here's what I do: run the :... : :Sure, I normally run these applications against a FreeBSD NFS server :with a four-way CCD, but this particular case was on a Slowaris :2.5 (sparcstation 1) machine with perfectly standard UFS. I haven't :been able to exhibit it on a local FFS disk. I also haven't been :able to exhibit it with a NetBSD NFS client, which is a bit odd :because all the code that my untrained eye found in /sys/nfs that :looked suspicious was the same on NetBSD and FreeBSD :) : : Mika : I'm not sure in what circumstances you are seeing the problem. You are seeing it locally on a sun and on a sun client with a FreeBSD NFS server? Is the file corrupted on the FreeBSD NFS server itself when you access it locally? -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications. (Please include portions of article in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message