From: NeilBrown <neilb@suse.de>
To: Richard Smits <R.Smits@tudelft.nl>
Cc: linux-nfs@vger.kernel.org
Subject: Re: rpc.mountd switch not working
Date: Wed, 7 Sep 2011 16:09:33 +1000 [thread overview]
Message-ID: <20110907160933.2a26ef3a@notabene.brown> (raw)
In-Reply-To: <4E64C8A0.6020806@tudelft.nl>
On Mon, 05 Sep 2011 15:03:28 +0200 Richard Smits <R.Smits@tudelft.nl> wrote:
> Hello,
>
> I have a question about the use of the following switch with rpc.mountd.
>
> -g or --manage-gids
>
> It has come to my attention that the use of this switch is not working
> well in Redhat v6. When I have a user who has a large group membership,
> the following errors appear, and the "cd" command hangs.
>
> Sep 5 14:50:04 srv043 rpc.mountd[2563]: qword_eol: fflush failed: errno
> 22 (Invalid argument)
>
> Process :
>
> root 2563 1 0 14:44 ? 00:00:00 rpc.mountd -g
>
> The use of 60 groups is working well, but we have some users with more
> than 100 groups, and those fails. For uid mapping we use Winbind.
>
> /etc/exports :
>
> /export server.company.com(rw,no_subtree_check,no_root_squash)
>
> Client fstab :
>
> server.company.com:/export /data nfs
> nolock,defaults,user 1 2
>
> Can anyone tell me what this error means ?
Probably means that the redhat package is missing upstream commit
9274e94db85bac04e170414cb8e0f4be271cde90
(which is from April this year, so not unlikely).
http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=5604b35a61e22930873ffc4e9971002f578e7978
NeilBrown
>
> Greetings .. Richard Smits
> --
> 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:[~2011-09-07 6:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 13:03 rpc.mountd switch not working Richard Smits
2011-09-07 6:09 ` NeilBrown [this message]
2011-09-08 8:19 ` Richard Smits
2011-09-08 15:11 ` Steve Dickson
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=20110907160933.2a26ef3a@notabene.brown \
--to=neilb@suse.de \
--cc=R.Smits@tudelft.nl \
--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.