From: David Flynn <davidf@rd.bbc.co.uk>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: David Flynn <davidf@rd.bbc.co.uk>, linux-nfs@vger.kernel.org
Subject: Re: NFSv4: "Viminfo file is not writable" -- stat(2) uid/gid incorrect
Date: Wed, 8 Dec 2010 21:19:31 +0000 [thread overview]
Message-ID: <20101208211930.GI20844@rd.bbc.co.uk> (raw)
In-Reply-To: <1291841129.3067.22.camel@heimdal.trondhjem.org>
* Trond Myklebust (Trond.Myklebust@netapp.com) wrote:
> Have you tried running the idmapper with the '-f -v -v' flags so you can
> log the translation upcalls? The default cache timeout is 10 minutes, so
> you shouldn't have to wait too long.
vc-r210-0:/# rpc.idmapd -f -v -v
rpc.idmapd: Expiration time is 600 seconds.
rpc.idmapd: Opened /proc/net/rpc/nfs4.nametoid/channel
rpc.idmapd: Opened /proc/net/rpc/nfs4.idtoname/channel
rpc.idmapd: New client: 0
rpc.idmapd: New client: 1
rpc.idmapd: New client: 10
rpc.idmapd: New client: 11
rpc.idmapd: New client: 12
rpc.idmapd: New client: 13
rpc.idmapd: New client: 14
rpc.idmapd: New client: 15
rpc.idmapd: New client: 2
rpc.idmapd: Opened /var/lib/nfs/rpc_pipefs/nfs/clnt2/idmap
rpc.idmapd: New client: 4
rpc.idmapd: New client: 5
rpc.idmapd: Opened /var/lib/nfs/rpc_pipefs/nfs/clnt5/idmap
rpc.idmapd: New client: 7
rpc.idmapd: New client: 8
rpc.idmapd: New client: 9
rpc.idmapd: New client: a
rpc.idmapd: New client: b
rpc.idmapd: New client: c
rpc.idmapd: New client: d
rpc.idmapd: New client: e
rpc.idmapd: New client: f
rpc.idmapd: Client 2: (user) name "root@rd.bbc.co.uk" -> id "0"
rpc.idmapd: Client 2: (group) name "other@rd.bbc.co.uk" -> id "20"
rpc.idmapd: Client 2: (user) name "davidf@rd.bbc.co.uk" -> id "1179"
rpc.idmapd: Client 2: (group) name "rd@rd.bbc.co.uk" -> id "1000"
These four translations occured at the very start of test, ie,
when bash was executed / ".file" truncated. There were no further
translations.
> While the open() call may indeed fail to set the uid/gid (because to do
> so would require an upcall right in the middle of an asynchronous RPC
> call), it should normally mark the inode as requiring revalidation if
> this is the case.
Where ought this occur (so we can validate that it is indeed the case)?
> The ensuing stat() should then trigger a GETATTR call on the wire, which
> will correct the uid/gid.
Is this possibly related to:
http://article.gmane.org/gmane.linux.nfs/37224 ?
Kind regards,
..david
next prev parent reply other threads:[~2010-12-08 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 15:33 NFSv4: "Viminfo file is not writable" -- stat(2) uid/gid incorrect David Flynn
2010-12-08 15:48 ` can't dump core on NFSv4 mounts David Flynn
2010-12-08 19:19 ` NFSv4: "Viminfo file is not writable" -- stat(2) uid/gid incorrect Trond Myklebust
2010-12-08 20:20 ` David Flynn
2010-12-08 20:45 ` Trond Myklebust
2010-12-08 21:19 ` David Flynn [this message]
2010-12-09 13:11 ` David Flynn
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=20101208211930.GI20844@rd.bbc.co.uk \
--to=davidf@rd.bbc.co.uk \
--cc=Trond.Myklebust@netapp.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox