public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 10:36:50 -0700	[thread overview]
Message-ID: <4A65FCB2.6080903@candelatech.com> (raw)
In-Reply-To: <1248196339.21343.8.camel@heimdal.trondhjem.org>

On 07/21/2009 10:12 AM, Trond Myklebust wrote:
> On Tue, 2009-07-21 at 09:49 -0700, Ben Greear wrote:
>> 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.
>
> So how should the client behave, when a screwed up server allows it to
> mount but starts returning illegal values for setclientid? The only
> thing I can see we could do is to tell the user EINSANESERVER...

Well, it could just fail the mount and give up and not overly spam
/var/log/messages in a tight loop perhaps?

> Now, we _should_ fix the wretched NFS server so that it doesn't do NFSv4
> mounts when there is no configured root partition. We _should_ also fix
> the damned thing so that it doesn't return illegal values.

Sounds fine to me.

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2009-07-21 17:36 UTC|newest]

Thread overview: 25+ 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
2009-07-21 16:49   ` Ben Greear
2009-07-21 17:12     ` Trond Myklebust
2009-07-21 17:36       ` Ben Greear [this message]
2009-07-21 17:59         ` Trond Myklebust
2009-07-21 18:01           ` Ben Greear
2009-07-21 18:28             ` Trond Myklebust
2009-07-21 18:32               ` Ben Greear
2009-07-21 18:54                 ` Trond Myklebust
2009-07-21 19:57                   ` Frans Pop
2009-07-21 21:17                 ` Trond Myklebust
2009-07-21 21:48                   ` Trond Myklebust
2009-07-21 21:50                     ` Ben Greear
2009-07-22 19:49                   ` Andy Adamson
2009-07-22 20:20                     ` Trond Myklebust
2009-07-22 21:32                       ` Andy Adamson
2009-07-22 21:47                         ` Trond Myklebust
2009-07-22 22:03                           ` Andy Adamson
2009-07-22 22:17                             ` Trond Myklebust
2009-07-22 22:26                               ` Andy Adamson
2009-07-21 19:23               ` Frans Pop
2009-07-21 19:54                 ` Trond Myklebust
2009-07-21 20:24                   ` Frans Pop
2009-07-21 17:49     ` Frans Pop

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=4A65FCB2.6080903@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox