From owner-freebsd-current Wed Apr 21 10:52:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 7C35715420; Wed, 21 Apr 1999 10:51:20 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id NAA01767; Wed, 21 Apr 1999 13:05:01 -0500 (EST) Date: Wed, 21 Apr 1999 13:04:58 -0500 (EST) From: Alfred Perlstein To: Matthew Dillon Cc: Bob Bishop , Wilko Bulte , current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Alright, who's the smart alleck that fixed NFS this last week? , :) , WAS: Re: solid NFS patch #6 avail for -current - need testers , files) In-Reply-To: <199904211720.KAA06806@apollo.backplane.com> 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 On Wed, 21 Apr 1999, Matthew Dillon wrote: > :2 questions I had: > : > :2) at BAFUG 2 or 3 months ago I, *cough* attempted to keep up with you > :an Julian talking about VM issues. :) Something you guys brought up > :was problems with mmap() + read()/write() no staying in sync and requireing > :an msync() to correctly syncronize. I really didn't understand how this > :could happen except recently I figured that my first question could be > :the answer. Does this problem only happen on NFS mounted dirs? Is it > :fixed? > : > :thanks again, > :-Alfred > > This should not be an issue any more for either UFS or NFS. If people > find that it is an issue, there's a bug somewhere that needs to be > addressed. This *was* an issue for NFS prior to the patch set. Ok, so is this what you and Julian were discussing about coherency issues? And it is fixed... cool. :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message