From owner-freebsd-current@FreeBSD.ORG Thu May 26 12:37:41 2005 Return-Path: X-Original-To: current@freebsd.org 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 4A07016A41F; Thu, 26 May 2005 12:37:41 +0000 (GMT) (envelope-from sten@blinkenlights.nl) Received: from ford.blinkenlights.nl (ford.blinkenlights.nl [213.204.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 114FC43D58; Thu, 26 May 2005 12:37:36 +0000 (GMT) (envelope-from sten@blinkenlights.nl) Received: from tea.blinkenlights.nl (tea.blinkenlights.nl [192.168.1.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ford.blinkenlights.nl (Postfix) with ESMTP id E42703F294; Thu, 26 May 2005 14:37:35 +0200 (CEST) Received: by tea.blinkenlights.nl (Postfix, from userid 101) id 763B323B; Thu, 26 May 2005 14:37:35 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by tea.blinkenlights.nl (Postfix) with ESMTP id 5C3BDE7; Thu, 26 May 2005 14:37:35 +0200 (CEST) Date: Thu, 26 May 2005 14:37:35 +0200 (CEST) From: Sten Spans To: ticso@cicely.de In-Reply-To: <20050526105806.GB80082@cicely12.cicely.de> Message-ID: References: <20050525223355.56551.qmail@web80601.mail.yahoo.com> <20050526010325.02415410.lehmann@ans-netz.de> <20050526085750.GZ80082@cicely12.cicely.de> <20050526105806.GB80082@cicely12.cicely.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org, stable@freebsd.org, Oliver Lehmann , Mohan Srinivasan Subject: Re: problems with nfs+TCP - Resource temporarily unavailable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 26 May 2005 12:37:41 -0000 On Thu, 26 May 2005, Bernd Walter wrote: >>> >>> This is absolutely known - TCP/nfs has bugs in realigning packets. >>> Don't use TCP on strong aligned architectures. >> >> Still a pr with a proper backtrace would be nice. >> Or does one exist already ? > > Not that I know. > I did know exactly when this happens years ago. > The backtrace as such will not help you as the panic happens much > later than the cause. > IIRC the basic problem was that the realignment code only fixes > a single missalignment, while theres a chance for more then one. > Verify nfs_realign in nfsserver and nfsclient to get an idea. > If you are interested - I've found a (non-working) patch that I wrote > for it, but the intention of it should be clear. > Sure. This is an nfsd specific problem, Or does nfsclient have issues as well ? I'll get a pr going to make sure that the issue is documented, and possibly narrowed down enough for other people to start painting a bikeshed about how it should be fixed. -- Sten Spans "There is a crack in everything, that's how the light gets in." Leonard Cohen - Anthem