All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: Boris Zuckerman <boris@ibrix.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: nfsd_rename() multiple export problem
Date: Fri, 31 Jul 2009 09:43:49 -0400	[thread overview]
Message-ID: <4A72F515.9070006@redhat.com> (raw)
In-Reply-To: <006c01ca115b$4a5808e0$df081aa0$@com>

Boris Zuckerman wrote:
> Hi,
> 
>  
> 
> This is probably a question for Peter Staubach. However, may be somebody
> else can help me too…
> 
>  
> 
> Once in a while under heavy load nfsd returns a NFSERR_XDEV from rename
> checking following condition:
> 
>  
> 
>       err = (rqstp->rq_vers == 2) ? nfserr_acces : nfserr_xdev;
> 
>       if (ffhp->fh_export != tfhp->fh_export)
> 
>             goto out;
> 
>  
> 
> Note that several lines later the similar check looks like this:
> 
>  
> 
>       host_err = -EXDEV;
> 
>       if (ffhp->fh_export->ex_path.mnt != tfhp->fh_export->ex_path.mnt)
> 
>             goto out_dput_new;
> 
>  
> 
> As you can see the code is not making any longer assumptions that
> fh_export must match, but rather is checking ex_path.mnt.
> 
> We reproduced the problem in-house and got following information: the
> source and the target directories are the same; Ibrix resolved them to
> the same dentry.
> 
> However, there are 2 different fh_exports. I noticed that one of them
> has expiry_time = 0x0 and  another has expiry_time = 0x4a6aee6d
> 
> Is it significant? Below is the complete dump of exports and svc_fh
> structurs. Please, let me know if you need more information.
> 
> I have the crash dump and can dig out anything you need.
> 

What version of the Linux kernel are you using?

	Thanx...

		ps
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

           reply	other threads:[~2009-07-31 14:45 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <006c01ca115b$4a5808e0$df081aa0$@com>]

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=4A72F515.9070006@redhat.com \
    --to=staubach@redhat.com \
    --cc=boris@ibrix.com \
    --cc=linux-fsdevel@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.