All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: linux-nfs@vger.kernel.org,
	Linux Filesystem Development <linux-fsdevel@vger.kernel.org>
Subject: 2.6.38-rc2... NFS sillyrename is broken...
Date: Tue, 25 Jan 2011 18:30:15 -0500	[thread overview]
Message-ID: <1295998215.6867.22.camel@heimdal.trondhjem.org> (raw)

Something in the recent VFS churn appears to have broken NFS
sillyrename.

Currently, when I try to unlink() a file that is being held open by
another process, I do indeed see that file getting renamed to
a .nfsxxxxxxx file, but when the file is closed, the .nfsxxxxx file
sticks around until I unlink() it again.

I'll have a look tomorrow at what is going wrong, but I figured I'd ask
on the list in case someone has a suspect...

Cheers
  Trond
-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@netapp.com
www.netapp.com


             reply	other threads:[~2011-01-25 23:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 23:30 Trond Myklebust [this message]
2011-01-26  8:20 ` 2.6.38-rc2... NFS sillyrename is broken J. R. Okajima
2011-01-26 20:14   ` Trond Myklebust
2011-01-26 20:43     ` Trond Myklebust
2011-01-26 20:43       ` Trond Myklebust
     [not found]       ` <1296074585.7127.33.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2011-01-26 23:50         ` Nick Piggin
2011-01-26 23:50           ` Nick Piggin
2011-01-26 23:59           ` Trond Myklebust
     [not found]             ` <1296086349.7127.55.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2011-01-27  0:44               ` Nick Piggin
2011-01-27  0:44                 ` Nick Piggin
     [not found]                 ` <AANLkTim1-dwNjTpyCi5qBjCer5vgPo4qSNfK7Htd_vfL-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-01-27  0:57                   ` Trond Myklebust
2011-01-27  0:57                     ` Trond Myklebust
     [not found]                     ` <1296089830.25999.1.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2011-01-27  1:25                       ` Nick Piggin
2011-01-27  1:25                         ` Nick Piggin
     [not found]                         ` <AANLkTim_JrZkD_D8HWXNr0qxjQ-=LKaAvzcH_w7A_T42-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-03-05 13:49                           ` Jeff Layton
2011-03-05 13:49                             ` Jeff Layton

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=1295998215.6867.22.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@netapp.com \
    --cc=linux-fsdevel@vger.kernel.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 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.