From: Tom Haynes <tdh@excfb.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Tom Haynes <tdh@excfb.com>, linux-nfs@vger.kernel.org
Subject: Re: Debugging mount failure with netgroup
Date: Mon, 7 Feb 2011 15:53:44 -0600 [thread overview]
Message-ID: <20110207215344.GA15778@adept.internal.excfb.com> (raw)
In-Reply-To: <20110207211917.GA3853@fieldses.org>
On Mon, Feb 07, 2011 at 04:19:17PM -0500, J. Bruce Fields wrote:
> On Mon, Feb 07, 2011 at 02:53:06PM -0600, Tom Haynes wrote:
> > I did google and did not find much on netgroups - but I did find
> > a bunch on "unmatched host".
> >
> > It seems to be black magic from some of the answers.
> >
> > And I agree:
> >
> > 1) Modified the export:
> > [root@adept /]# more /etc/exports
> > /fooper @adeptya(rw,insecure,no_root_squash,sync)
>
> So it was probably the "insecure"?
Sorry, I forgot to mention after every step that I tried
the mount and it failed. It was only restarting nfs
that worked.
I'd have to check to see what port number the requests
are coming in on, but I don't think it is this.
And I've actually got the system horked up right now -
I restarted one time too many. Frustrating as there isn't
anything logged beyond "unmatched host".
>
> Are we returning the right error to the mount client in that case?
>
> And I suppose the logged error should be more helpful. I'm not really
> sure mountd should be logging every mount failure by default, but if you
> request it, it should at be able to tell you the reason for the failure.
>
> --b.
>
--
Tom Haynes
ex-cfb
next prev parent reply other threads:[~2011-02-07 21:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 19:56 Debugging mount failure with netgroup Tom Haynes
2011-02-07 20:12 ` J. Bruce Fields
2011-02-07 20:53 ` Tom Haynes
2011-02-07 21:19 ` J. Bruce Fields
2011-02-07 21:53 ` Tom Haynes [this message]
2011-02-07 21:59 ` J. Bruce Fields
2011-02-07 23:21 ` Tom Haynes
2011-02-09 0:23 ` J. Bruce Fields
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=20110207215344.GA15778@adept.internal.excfb.com \
--to=tdh@excfb.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
/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.