From owner-freebsd-stable@FreeBSD.ORG Sat Feb 13 10:39:10 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63FA41065679 for ; Sat, 13 Feb 2010 10:39:10 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id BBD2C8FC14 for ; Sat, 13 Feb 2010 10:39:09 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id o1DA96Rw058650 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 13 Feb 2010 11:09:06 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.3/8.14.3) with ESMTP id o1DA93lK052738 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 13 Feb 2010 11:09:03 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id o1DA93iY048987; Sat, 13 Feb 2010 11:09:03 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id o1DA92Jo048986; Sat, 13 Feb 2010 11:09:02 +0100 (CET) (envelope-from ticso) Date: Sat, 13 Feb 2010 11:09:02 +0100 From: Bernd Walter To: alan bryan Message-ID: <20100213100902.GH43625@cicely7.cicely.de> References: <247310.48932.qm@web50506.mail.re2.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <247310.48932.qm@web50506.mail.re2.yahoo.com> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: freebsd-hackers@freebsd.org, Dmitry Marakasov , freebsd-stable@freebsd.org, Rick Macklem Subject: Re: NFS write corruption on 8.0-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Feb 2010 10:39:10 -0000 On Fri, Feb 12, 2010 at 04:08:55PM -0800, alan bryan wrote: > > > --- On Fri, 2/12/10, Rick Macklem wrote: > > > From: Rick Macklem > > Subject: Re: NFS write corruption on 8.0-RELEASE > > To: "Dmitry Marakasov" > > Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org, "John Baldwin" > > Date: Friday, February 12, 2010, 11:12 AM > > > > > > On Fri, 12 Feb 2010, Dmitry Marakasov wrote: > > > > > > > > I'm planning a massive testing for this weekend, > > including removing > > > soft mount option and trying linux client/server. > > > > > > Btw, I forgot to mention that I'm experiencing other > > NFS problems from > > > time to time, including "death" of a mount (that is, > > all processes that > > > try to access it freeze; this cures itself in some > > time with a message > > > "server is alive again"). Also I've seen another > > strange thing - not > > > only the mount dies but the network is flooded with > > NFS traffic. > > > Last time I've seen it quite a while ago, so I don't > > remember the > > > circumstances and direction of the traffic. > > > > > There are some patches at: > >     http://people.freebsd.org/~rmacklem > > that may be relevant if you are using vanilla FreeBSD-8.0. > > (They're all > > now in stable/8, but are post-release of 8.0.) > > > > rick > > > > _______________________________________________ > > freebsd-stable@freebsd.org > > mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > > > This is interesting: > > "I've seen another strange thing - not only the mount dies but the network is flooded with NFS traffic." You might be able to see NFS flooding with: Write file on client. rm the file during the write on the server. The client now gets IO-errors, but keeps trying forever. Maybe it depends on the mechanism the client application uses to write the file. I never reported because my client is an old 7.0-stable system. I originally noticed it when downloading files with seamonkey on my client and mv it on the server to another partition before it was completely downloaded. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.