Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: devzero@web.de
Cc: Neil Brown <neilb@suse.de>, NFS@lists.sourceforge.net
Subject: Re: stale nfs file handle with exported loopback mounts
Date: Fri, 2 Nov 2007 15:24:43 -0400	[thread overview]
Message-ID: <20071102192443.GG15595@fieldses.org> (raw)
In-Reply-To: <20071102192317.GF15595@fieldses.org>

On Fri, Nov 02, 2007 at 03:23:17PM -0400, J. Bruce Fields wrote:
> On Fri, Nov 02, 2007 at 08:06:58PM +0100, devzero@web.de wrote:
> > hi!
> > 
> > it seems i was having weird mail problems with sending mails trough my webmailer - at least two followups with attachments seem to be lost on sending and are not in my sent folder anymore....
> > 
> > anyway - here is a second try, but probably worse than what i have written before :)
> > 
> > 
> > first off, thanks for the patch Neil, things look _much_ better now and exporting loopback mounts now basiscally works again.
> > nice to see that my posting helped finding bugs.
> > 
> > maybe i have two more bugs for you :)
> > 
> > i have loopback mounts on the server and exported the parent dir with crossmnt option.
> > 
> > after mounting for the first time on the client, i`m getting "Invalid argument" for each loopback-mounted dir, if i do an ls -la on /mnt.
> > this only happens _once_ and seems to be a server problem, because i can reboot the client and remount , i never see that errors again.
> 
> >From a quick look at the trace (thanks)--there's some getacl calls that
> return EINVAL, then a few milliseconds later a second reply returns with
> the original data.  That looks suspiciously like a reply being sent when
> the request was also deferred pending the upcall to deal with the newly
> encountered filesystem.  Sure enough, in
> fs/nfs/nfs3acl.c:nfsd3_proc_getacl(), there's
> 
> 	 if ((nfserr = fh_verify(rqstp, &resp->fh, 0, MAY_NOP)))
> 		RETURN_STATUS(nfserr_inval);
> 
> Change that nfserr_inval to an nfserr (here and in
> fs/nfs/nfs2acl.c:nfsd_proc_getacl()), and maybe the problem will go
> away.

(I've been seeing some odd spurious replayed replies in the nfsv4 case
as well, by the way--I suspect it's a similar problem, but haven't had
the chance to track it down yet....)

--b.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-11-02 19:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02 19:06 stale nfs file handle with exported loopback mounts devzero
2007-11-02 19:23 ` J. Bruce Fields
2007-11-02 19:24   ` J. Bruce Fields [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-11-10 15:14 devzero
2007-11-02 19:37 devzero
2007-11-02 19:42 ` J. Bruce Fields
2007-11-04 20:30   ` J. Bruce Fields
2007-11-05  9:59     ` Andreas Gruenbacher
2007-10-31 22:50 devzero
2007-11-01  4:26 ` Neil Brown
2007-10-31 22:19 devzero
2007-10-31 22:39 ` J. Bruce Fields
2007-10-31 20:46 devzero
2007-10-31 20:57 ` J. Bruce Fields
2007-10-30 20:05 devzero
2007-10-27 16:13 devzero
2007-10-30  5:14 ` Neil Brown

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=20071102192443.GG15595@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=NFS@lists.sourceforge.net \
    --cc=devzero@web.de \
    --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