Return-Path: <linux-kernel-owner+w=401wt.eu-S1753081AbZGUT5R@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753081AbZGUT5R (ORCPT <rfc822;w@1wt.eu>);
	Tue, 21 Jul 2009 15:57:17 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752469AbZGUT5Q
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Tue, 21 Jul 2009 15:57:16 -0400
Received: from Cpsmtpm-eml107.kpnxchange.com ([195.121.3.11]:52005 "EHLO
	CPSMTPM-EML107.kpnxchange.com" rhost-flags-OK-OK-OK-OK)
	by vger.kernel.org with ESMTP id S1751973AbZGUT5Q (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 21 Jul 2009 15:57:16 -0400
From: Frans Pop <elendil@planet.nl>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: Error mounting FC8 NFS server with 2.6.31-rc3 NFSv4 client.
Date: Tue, 21 Jul 2009 21:57:13 +0200
User-Agent: KMail/1.9.9
Cc: greearb@candelatech.com, linux-kernel@vger.kernel.org,
       linux-nfs@vger.kernel.org
References: <4A64EB1F.4000602@candelatech.com> <1248178527.5222.0.camel@heimdal.trondhjem.org> <4A65F184.5060802@candelatech.com> <1248196339.21343.8.camel@heimdal.trondhjem.org> <4A65FCB2.6080903@candelatech.com> <1248199140.21343.17.camel@heimdal.trondhjem.org> <4A660295.9020807@candelatech.com> <1248200897.21343.19.camel@heimdal.trondhjem.org> <4A6609A9.3000504@candelatech.com> <4A6609A9.3000504@candelatech.com> <1248202462.21343.21.camel@heimdal.trondhjem.org>
In-reply-To: <1248202462.21343.21.camel@heimdal.trondhjem.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907212157.14781.elendil@planet.nl>
X-OriginalArrivalTime: 21 Jul 2009 19:57:15.0482 (UTC) FILETIME=[71F7ABA0:01CA0A3D]
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1065
Lines: 31

Trond Myklebust wrote:
> OK. Then the NFSv4.1 merge has screwed up the state management. We do
> NOT want to hold client id state on the server when there is no file
> state...

Hmm. I doubt that as I can reproduce the same problem (at least the mount 
hanging, not necessarily the errors) with .30, which I presume is before 
the merge.

I have seen the errors too, but that may have been with 2.6.31 (though 
definitely without NFS_V4_1). I seem unable to reproduce those with .30.

On the server (.30) in /etc/exportfs:
/srv/exports         10.19.66.0/24(rw,subtree_check,sync,mp,nohide)
/srv/exports/data    10.19.66.0/24(rw,subtree_check,sync,mp,nohide)

# exportfs
/srv/exports         10.19.66.0/24
/srv/exports/data    10.19.66.0/24

On the client (.30.2):
# mount thorin:/data /mnt -t nfs4
<hangs>

Cheers,
FJP
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/