Linux NFS development
 help / color / mirror / Atom feed
From: Frank van Maarseveen <frankvm@frankvm.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Linux NFS mailing list <linux-nfs@vger.kernel.org>
Subject: Re: V3 ACCESS call fails after server reboot
Date: Mon, 10 Dec 2007 19:17:09 +0100	[thread overview]
Message-ID: <20071210181709.GA9326@janus> (raw)
In-Reply-To: <20071210174117.GK17209@fieldses.org>

On Mon, Dec 10, 2007 at 12:41:17PM -0500, J. Bruce Fields wrote:
> On Mon, Dec 10, 2007 at 06:20:04PM +0100, Frank van Maarseveen wrote:
> > Tested on 2.6.22.10 and 2.6.23.9, client and server running same version.
> > export options: rw,sync,no_root_squash,no_subtree_check,mp
> > 
> > After a substantial amount of time (days) but also after a server
> > reboot a process loses access to its current working directory when
> > access to a parent directory two (or more) levels up has been revoked:
> > 
> > 	$ cd /mnt
> > 	$ mkdir -p a/b/c
> > 	$ cd a/b/c
> > 	$ chmod 0 ../..
> > 	$ ls -a
> > 	. ..
> > 	$
> > 		(wait a loong time or reboot server)
> > 	$ ls -a
> > 	ls: .: Permission denied
> > 
> > Network traffic capture showed a V3 ACCESS call for above "." failing
> > on the server after the reboot with NFS3ERR_ACCES. It succeeded before.
> > 
> > I have the impression the server is internally rechecking the entire
> > path when its caches have been flushed. This behavior is problematic
> > for daemons which change uid, for example.
> 
> What are your export options?  (Do you have nosubtreecheck turned on?)
yes, see above export options.

-- 
Frank

      reply	other threads:[~2007-12-10 18:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 17:20 V3 ACCESS call fails after server reboot Frank van Maarseveen
2007-12-10 17:41 ` J. Bruce Fields
2007-12-10 18:17   ` Frank van Maarseveen [this message]

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=20071210181709.GA9326@janus \
    --to=frankvm@frankvm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox