All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: wangjing <wangjing@300.cn>
Cc: linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: may i ask a question about nfs fs ? thanks a lot.
Date: Thu, 2 Feb 2012 11:47:25 +0200	[thread overview]
Message-ID: <4F2A5BAD.4000609@panasas.com> (raw)
In-Reply-To: <201202020009007716206@300.cn>

On 02/01/2012 06:09 PM, wangjing wrote:
> 
> may i ask a question? thanks a lot.
> 
> the background
>    1、Linux fs has   /nfsmnt/work_pub/web and /nfsmnt/work_inwork/web ,they use NFS V3 mount
>    2、there is many process will read and write files in the dir /nfsmnt/work_pub/web 
>    3、cron will del  all files in dir  /nfsmnt/work_pub/web in period,and will copy all the files which in the dir /nfsmnt/work_inwork/web 
> 
> in some times delete all files in  /nfsmnt/work_pub/web will faild ,because there is some .nfsXXXX
> 
> 
> 
> My question is :can i modify nfs_sillyrename funncion  in the fs/nfs/dir.c , general all .nfsXXX in /tmp,and make kernel ?
> 
> 

You can't do this. /tmp on the client is on a different superblock than the nfs mount, and the point of
sillyrename is that it is a rename and not a move. (i.e same inode)

The /tmp on the server is not even accessible on the client, which does the sillyrename.

You'll have to better your scripts to loop and delete until all  .nfsXXXX go away because
these are temporarily there until the application on the client stops using the file.

Cheers
Boaz

  parent reply	other threads:[~2012-02-02  9:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201202012212229514260@300.cn>
2012-02-01 16:09 ` may i ask a question about nfs fs ? thanks a lot wangjing
2012-02-02  1:30   ` Jim Rees
2012-02-02  2:14   ` wangjing
2012-02-02  9:47   ` Boaz Harrosh [this message]
2012-03-07 10:11   ` sword

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=4F2A5BAD.4000609@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=wangjing@300.cn \
    /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.