[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1248199140.21343.17.camel@heimdal.trondhjem.org>
Date: Tue, 21 Jul 2009 13:59:00 -0400
From: Trond Myklebust <trond.myklebust@....uio.no>
To: Ben Greear <greearb@...delatech.com>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
linux-nfs@...r.kernel.org
Subject: Re: Error mounting FC8 NFS server with 2.6.31-rc3 NFSv4 client.
On Tue, 2009-07-21 at 10:36 -0700, Ben Greear wrote:
> 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?
This doesn't happen at mount time. It happens when you open a file.
Trond
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists