All of lore.kernel.org
 help / color / mirror / Atom feed
From: Per Buer <perbu@linpro.no>
To: nfs@lists.sourceforge.net
Subject: Does nfsd.o handle overwriting of files properly?
Date: Fri, 13 Aug 2004 09:04:26 +0200	[thread overview]
Message-ID: <200408130904.26180.perbu@linpro.no> (raw)

Hi.

We have a daemon which does the following. Create a new file "foo" and renames 
this file to "bar". This happens on a nfs volume. The problem seems to be 
that we get "stale NFS handle" right after "bar" is overwritten.

I guess the directory is cached and so the dentry points to an non-existing 
inode (as the old "bar" is deleted when the ref-count hits zero). 

Server: RHEL AS 2.1 (2.4.9 with lots and lots of pathes)
Client: RHEL ES 3.0 (2.4.21with lots and lots of pathes)

I fix could be to keep an link to the old "bar" hanging around for 30s or so - 
but I consider that a somewhat dirty work-around.

Is there anything else I can do to mend this?

-- 
There are only 10 different kinds of people in the world, 
those who understand binary, and those who don't.


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2004-08-13  7:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-13  7:04 Per Buer [this message]
2004-08-13 16:06 ` Does nfsd.o handle overwriting of files properly? Trond Myklebust

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=200408130904.26180.perbu@linpro.no \
    --to=perbu@linpro.no \
    --cc=nfs@lists.sourceforge.net \
    /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.