Linux NFS development
 help / color / mirror / Atom feed
From: Frank Cusack <fcusack@fcusack.com>
To: nfs@lists.sourceforge.net, trond.myklebust@fys.uio.no
Subject: Re: nfs_refresh_inode: inode number mismatch (bug)
Date: Mon, 2 Jun 2003 02:46:25 -0700	[thread overview]
Message-ID: <20030602024625.A19179@google.com> (raw)
In-Reply-To: <20030602013731.B18730@google.com>; from fcusack@fcusack.com on Mon, Jun 02, 2003 at 01:37:31AM -0700

On Mon, Jun 02, 2003 at 01:37:31AM -0700, Frank Cusack wrote:
> I've found an issue with nfs_rmdir(), at least that's where I think it is.

A little more info ...

This seems related to nfs3, and I'm going to guess readdirplus.  If
I mount as nfsv2, I don't see the problem.

It just struck me that there are a lot of readdirplus-related logs just
before the "bug".  I didn't think anything of it (because, *of course*
there is a bunch of activity there) but in a rare moment of clarity I
figured I should try v2.

I'll continue to look at this tomorrow, but I'm sure Trond or one of
the wizards here will instantly know where the problem is. :-)

/fc


-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2003-06-02  9:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-02  8:37 nfs_refresh_inode: inode number mismatch (bug) Frank Cusack
2003-06-02  9:46 ` Frank Cusack [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=20030602024625.A19179@google.com \
    --to=fcusack@fcusack.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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