From: "J. Bruce Fields" <bfields@fieldses.org>
To: Sander Smeenk <ssmeenk@freshdot.net>
Cc: linux-nfs@vger.kernel.org
Subject: Re: rpc.mountd --manage-gids breaks on UID differences
Date: Tue, 17 Nov 2009 15:08:31 -0500 [thread overview]
Message-ID: <20091117200831.GA3969@fieldses.org> (raw)
In-Reply-To: <20091117153928.GA12493-N0d2glMUd7m2/GFIlvLUCQ@public.gmane.org>
On Tue, Nov 17, 2009 at 04:39:28PM +0100, Sander Smeenk wrote:
> Aparently this has to do with UIDs being different on the nfs-server and
> the nfs-client as i discovered debugging this problem in two VMs. It's
> quite easy to reproduce and also seems to happen if the user on the
> clientmachine is nonexistant on the servermachine.
>
> Disabling '--manage-gids' and remouting, restarting or rebooting
> completely fixes the problem. Reintroducing '--manage-gids' breaks it
> again.
Just from those symptoms it sounds to me like rpc.mountd isn't
responding to upcalls when asked about a uid for which there's no
account on the server. It should be returning a negative response
immediately.
(I assume your server isn't using ldap or nis or something that could
cause lookups of a uid to take a long time?)
--b.
> It appears to me '--manage-gids' is completely broken in this setup, or
> i misunderstand what --manage-gids does, completely. I haven't tried
> this on newer kernels (2.6.31-14-generic f.e.).
>
> I do have kernel debug logs during broken and working NFS transactions
> which i got by echoing the correct bitmask to /proc/sys/sunrpc/*debug.
>
> http://www.freshdot.net/tmp/client-broken-syslog
> http://www.freshdot.net/tmp/server-broken-syslog
> vs
> http://www.freshdot.net/tmp/client-working-syslog
> http://www.freshdot.net/tmp/server-working-syslog
>
> Is this behaviour intended?
> Hope to hear from you!
>
> With regards,
> Sander Smeenk.
> --
> | When you've seen one shopping center you've seen a mall.
> | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-11-17 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 15:39 rpc.mountd --manage-gids breaks on UID differences Sander Smeenk
[not found] ` <20091117153928.GA12493-N0d2glMUd7m2/GFIlvLUCQ@public.gmane.org>
2009-11-17 20:08 ` J. Bruce Fields [this message]
2009-11-17 20:43 ` Sander Smeenk
2009-11-18 21:31 ` J. Bruce Fields
2009-11-26 9:16 ` Sander Smeenk
[not found] ` <20091126091657.GL15295-N0d2glMUd7m2/GFIlvLUCQ@public.gmane.org>
2009-11-27 19:05 ` 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=20091117200831.GA3969@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=ssmeenk@freshdot.net \
/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