From owner-freebsd-stable@FreeBSD.ORG Tue Oct 27 17:22:43 2009 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 B7A28106568B for ; Tue, 27 Oct 2009 17:22:43 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from mail-gx0-f218.google.com (mail-gx0-f218.google.com [209.85.217.218]) by mx1.freebsd.org (Postfix) with ESMTP id 7309F8FC29 for ; Tue, 27 Oct 2009 17:22:43 +0000 (UTC) Received: by gxk10 with SMTP id 10so921512gxk.3 for ; Tue, 27 Oct 2009 10:22:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=YNyUiOKEmuLB4IgfTN5ChwzV9c5DL4tjfIGbvEy4MQ4=; b=qL/YseHPoACEGGcAbuZaQhLmLx3FY9t0D8rk6s8kby6RHZ/KMBjIyFXvHu9NBETV6l wpAVPXLDHmcZudgKaUJS+n8YV7xXh+aIi5zLrofvK4jfkzuBTxfm5vlvMnkyO88oDz5O XseXw9e3pMSCV70S4WCv2adrz4rey9gzXVdtw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=GHiJ+Zt4D+LjJTzuduGwvuYbS+duiUwPBEEa7cVJp/9mTJmjhBHXZPzsv+sH/FKfZT IsL5UbzoI/mCcL9KZENM6qRCe47jYZnKPTEMY95wsn+kWJaFZCuhACy+tvDPcxDzBna1 HI17IDcHJunKo3pD0Tqo069aFOfn7bbevi2OE= MIME-Version: 1.0 Received: by 10.150.113.13 with SMTP id l13mr26905059ybc.248.1256662871118; Tue, 27 Oct 2009 10:01:11 -0700 (PDT) In-Reply-To: <20091027164159.GU841@twoquid.cs.ru.nl> References: <20091027164159.GU841@twoquid.cs.ru.nl> Date: Tue, 27 Oct 2009 18:01:11 +0100 Message-ID: From: Claus Guttesen To: Olaf Seibert Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable@freebsd.org, Olaf Seibert Subject: Re: 8.0-RC1 NFS client timeout issue X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Oct 2009 17:22:43 -0000 > I see an annoying behaviour with NFS over TCP. It happens both with nfs > and newnfs. This is with FreeBSD/amd64 8.0-RC1 as client. The server is > some Linux or perhaps Solaris, I'm not entirely sure. I used nfs with tcp on a 7.2-client without problems on a solaris nfs-server. When I upgraded to RC1 I had 'server not responding - alive again' messages so I swithced to udp which works flawlessly. I haven't had time to investigate it though. -- regards Claus When lenity and cruelty play for a kingdom, the gentler gamester is the soonest winner. Shakespeare twitter.com/kometen