From: "J. Bruce Fields" <bfields@fieldses.org>
To: NeilBrown <neilb@suse.de>,
"Myklebust, Trond" <Trond.Myklebust@netapp.com>,
NFS <linux-nfs@vger.kernel.org>
Subject: Re: Inconsistency when mounting a directory that 'world' cannot access.
Date: Mon, 8 Oct 2012 10:18:39 -0400 [thread overview]
Message-ID: <20121008141839.GA27230@fieldses.org> (raw)
In-Reply-To: <20121008135452.GA14785@us.ibm.com>
On Mon, Oct 08, 2012 at 08:54:52AM -0500, Malahal Naineni wrote:
> NeilBrown [neilb@suse.de] wrote:
> > Mount with NFSv4 and it takes about the same. However:
> >
> > .....
> > drwxr-xr-x 2 4294967294 root 4096 Oct 8 16:19 2974
> > drwxr-xr-x 2 4294967294 root 4096 Oct 8 16:19 2975
> > drwxr-xr-x 2 4294967294 root 4096 Oct 8 16:19 2976
> > drwxr-xr-x 2 4294967294 root 4096 Oct 8 16:19 2977
> > drwxr-xr-x 2 4294967294 root 4096 Oct 8 16:19 2978
> > drwxr-xr-x 2 u2979 root 4096 Oct 8 16:19 2979
> > drwxr-xr-x 2 u2980 root 4096 Oct 8 16:19 2980
> > drwxr-xr-x 2 4294967294 root 4096 Oct 8 16:19 2981
> > drwxr-xr-x 2 4294967294 root 4096 Oct 8 16:19 2982
> > drwxr-xr-x 2 4294967294 root 4096 Oct 8 16:19 2983
> > drwxr-xr-x 2 4294967294 root 4096 Oct 8 16:19 2984
> > drwxr-xr-x 2 4294967294 root 4096 Oct 8 16:19 2985
> > drwxr-xr-x 2 4294967294 root 4096 Oct 8 16:19 2986
> > ....
> >
> >
> > tcpdump shows the server is returning the write stuff, but something if going
> > wrong on the client. I've tried unmounting/remounting and killing/restarting
> > rpc.idmapd.
>
> As you know 4294967294 is (-2, nfs nobody), I have seen this issue with NFS
> server sending numeric ids by default in AUTH_SYS (commit
> e9541ce8efc22c233a045f091c2b969923709038), but the client can't handle
> them (lack of commit 5cf36cfdc8caa2724738ad0842c5c3dd02f309dc in client
> code).
>
> I hand patched server commit, but my client was an older one. That is
> how I got into my issue. Not sure, if you are running into a similar
> issue.
Oh, could be--but then why would some of the id's still be mapped
correctly?
--b.
next prev parent reply other threads:[~2012-10-08 14:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 1:23 Inconsistency when mounting a directory that 'world' cannot access NeilBrown
2012-10-01 15:43 ` J. Bruce Fields
2012-10-02 2:38 ` NeilBrown
2012-10-02 14:33 ` J. Bruce Fields
2012-10-03 3:46 ` NeilBrown
2012-10-03 15:13 ` J. Bruce Fields
2012-10-03 15:48 ` Myklebust, Trond
2012-10-03 16:27 ` J. Bruce Fields
2012-10-03 22:46 ` NeilBrown
2012-10-04 16:07 ` J. Bruce Fields
2012-10-08 6:03 ` NeilBrown
2012-10-08 11:42 ` Steve Dickson
2012-10-08 12:20 ` J. Bruce Fields
2012-10-09 0:30 ` NeilBrown
2012-10-08 12:19 ` J. Bruce Fields
2012-10-08 13:54 ` Malahal Naineni
2012-10-08 14:18 ` J. Bruce Fields [this message]
2012-10-08 15:26 ` Malahal Naineni
2012-10-09 0:33 ` NeilBrown
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=20121008141839.GA27230@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).