From: Frans Pop <elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: greearb@candelatech.com, linux-kernel@vger.kernel.org,
linux-nfs@vger.kernel.org
Subject: Re: Error mounting FC8 NFS server with 2.6.31-rc3 NFSv4 client.
Date: Tue, 21 Jul 2009 21:57:13 +0200 [thread overview]
Message-ID: <200907212157.14781.elendil@planet.nl> (raw)
In-Reply-To: <1248202462.21343.21.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
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
WARNING: multiple messages have this Message-ID (diff)
From: Frans Pop <elendil@planet.nl>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: greearb@candelatech.com, linux-kernel@vger.kernel.org,
linux-nfs@vger.kernel.org
Subject: Re: Error mounting FC8 NFS server with 2.6.31-rc3 NFSv4 client.
Date: Tue, 21 Jul 2009 21:57:13 +0200 [thread overview]
Message-ID: <200907212157.14781.elendil@planet.nl> (raw)
In-Reply-To: <1248202462.21343.21.camel@heimdal.trondhjem.org>
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
next prev parent reply other threads:[~2009-07-21 19:57 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 22:09 Error mounting FC8 NFS server with 2.6.31-rc3 NFSv4 client Ben Greear
2009-07-21 12:15 ` Trond Myklebust
[not found] ` <1248178527.5222.0.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-07-21 16:49 ` Ben Greear
2009-07-21 16:49 ` Ben Greear
2009-07-21 17:12 ` Trond Myklebust
[not found] ` <1248196339.21343.8.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-07-21 17:36 ` Ben Greear
2009-07-21 17:36 ` Ben Greear
2009-07-21 17:59 ` Trond Myklebust
[not found] ` <1248199140.21343.17.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-07-21 18:01 ` Ben Greear
2009-07-21 18:01 ` Ben Greear
2009-07-21 18:28 ` Trond Myklebust
[not found] ` <1248200897.21343.19.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-07-21 18:32 ` Ben Greear
2009-07-21 18:32 ` Ben Greear
2009-07-21 18:54 ` Trond Myklebust
[not found] ` <1248202462.21343.21.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-07-21 19:57 ` Frans Pop [this message]
2009-07-21 19:57 ` Frans Pop
2009-07-21 21:17 ` Trond Myklebust
[not found] ` <1248211050.21343.38.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-07-21 21:48 ` Trond Myklebust
2009-07-21 21:48 ` Trond Myklebust
[not found] ` <1248212939.5034.1.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-07-21 21:50 ` Ben Greear
2009-07-21 21:50 ` Ben Greear
2009-07-22 19:49 ` Andy Adamson
2009-07-22 19:49 ` Andy Adamson
2009-07-22 20:20 ` Trond Myklebust
[not found] ` <1248294013.5234.35.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-07-22 21:32 ` Andy Adamson
2009-07-22 21:32 ` Andy Adamson
2009-07-22 21:47 ` Trond Myklebust
[not found] ` <1248299236.9202.3.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-07-22 22:03 ` Andy Adamson
2009-07-22 22:03 ` Andy Adamson
2009-07-22 22:17 ` Trond Myklebust
[not found] ` <1248301062.9202.11.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2009-07-22 22:26 ` Andy Adamson
2009-07-22 22:26 ` Andy Adamson
2009-07-21 19:23 ` Frans Pop
2009-07-21 19:23 ` Frans Pop
[not found] ` <200907212123.08790.elendil-EIBgga6/0yRmR6Xm/wNWPw@public.gmane.org>
2009-07-21 19:54 ` Trond Myklebust
2009-07-21 19:54 ` Trond Myklebust
2009-07-21 20:24 ` Frans Pop
2009-07-21 17:49 ` Frans Pop
2009-07-21 17:49 ` Frans Pop
-- strict thread matches above, loose matches on Subject: below --
2009-07-20 21:43 Ben Greear
2009-07-20 23:02 ` Ben Greear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200907212157.14781.elendil@planet.nl \
--to=elendil-eibgga6/0yrmr6xm/wnwpw@public.gmane.org \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.