Date: Thu, 26 May 2005 14:37:35 +0200 (CEST) From: Sten Spans <sten@blinkenlights.nl> To: ticso@cicely.de Cc: current@freebsd.org, stable@freebsd.org, Oliver Lehmann <lehmann@ans-netz.de>, Mohan Srinivasan <mohan_srinivasan@yahoo.com> Subject: Re: problems with nfs+TCP - Resource temporarily unavailable Message-ID: <Pine.SOC.4.61.0505261429530.18365@tea.blinkenlights.nl> In-Reply-To: <20050526105806.GB80082@cicely12.cicely.de> References: <20050525223355.56551.qmail@web80601.mail.yahoo.com> <20050526010325.02415410.lehmann@ans-netz.de> <20050526085750.GZ80082@cicely12.cicely.de> <Pine.SOC.4.61.0505261243440.18365@tea.blinkenlights.nl> <20050526105806.GB80082@cicely12.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SOC.4.61.0505261429530.18365>