From owner-freebsd-current@FreeBSD.ORG Thu Dec 23 21:27:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31BAC16A4CE for ; Thu, 23 Dec 2004 21:27:03 +0000 (GMT) Received: from web80603.mail.yahoo.com (web80603.mail.yahoo.com [66.218.79.92]) by mx1.FreeBSD.org (Postfix) with SMTP id 2122843D2D for ; Thu, 23 Dec 2004 21:27:03 +0000 (GMT) (envelope-from mohan_srinivasan@yahoo.com) Message-ID: <20041223212703.37253.qmail@web80603.mail.yahoo.com> Received: from [207.126.239.39] by web80603.mail.yahoo.com via HTTP; Thu, 23 Dec 2004 13:27:03 PST Date: Thu, 23 Dec 2004 13:27:03 -0800 (PST) From: Mohan Srinivasan To: alex.wilkinson@dsto.defence.gov.au, freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: NFS flakiness since @ last Friday X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Dec 2004 21:27:03 -0000 NFS Direct IO completely bypasses the client cache and is useful in situations where - The application does caching. - The application knows that the data read/written is not going to be accessed again anytime soon. I did stress testing of NFS direct IO, but need to replicate the environments/tests that you guys are seeing problems in. I am going to turn off NFS direct IO support till the problems are fixed. mohan