From: Ben Greear <greearb@candelatech.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel <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 09:49:08 -0700 [thread overview]
Message-ID: <4A65F184.5060802@candelatech.com> (raw)
In-Reply-To: <1248178527.5222.0.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
On 07/21/2009 05:15 AM, Trond Myklebust wrote:
>
> What does /var/lib/nfs/v4recovery look like on the server?
The server was misconfigured, but I still think the client should
behave better in this case. If you cannot reproduce it, let me know
and I can try to be more specific. If you still want the v4recovery
information, let me know and I'll send it.
I had my /etc/exports looking like this on the file-server:
/export/tmp 192.168.100.0/24(rw)
When I changed it to be:
/export/tmp 192.168.100.0/24(rw,fsid=0)
And mounted 192.168.100.6:/ instead of 192.168.100.6:/export/tmp
then it mounts properly and appears to work just fine.
If I leave file-server configured properly with fsid=0, but try
to mount 192.168.100.6:/export/tmp then I get an error about
no such file or directory, which also appears to be correct
behaviour.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
WARNING: multiple messages have this Message-ID (diff)
From: Ben Greear <greearb@candelatech.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel <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 09:49:08 -0700 [thread overview]
Message-ID: <4A65F184.5060802@candelatech.com> (raw)
In-Reply-To: <1248178527.5222.0.camel@heimdal.trondhjem.org>
On 07/21/2009 05:15 AM, Trond Myklebust wrote:
>
> What does /var/lib/nfs/v4recovery look like on the server?
The server was misconfigured, but I still think the client should
behave better in this case. If you cannot reproduce it, let me know
and I can try to be more specific. If you still want the v4recovery
information, let me know and I'll send it.
I had my /etc/exports looking like this on the file-server:
/export/tmp 192.168.100.0/24(rw)
When I changed it to be:
/export/tmp 192.168.100.0/24(rw,fsid=0)
And mounted 192.168.100.6:/ instead of 192.168.100.6:/export/tmp
then it mounts properly and appears to work just fine.
If I leave file-server configured properly with fsid=0, but try
to mount 192.168.100.6:/export/tmp then I get an error about
no such file or directory, which also appears to be correct
behaviour.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2009-07-21 16:49 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 [this message]
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
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=4A65F184.5060802@candelatech.com \
--to=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.