All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Chow <davidchow@shaolinmicro.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Problems of lookup_revalidate
Date: Thu, 29 Aug 2002 17:26:32 +0800	[thread overview]
Message-ID: <3D6DE8C8.3080601@shaolinmicro.com> (raw)
In-Reply-To: shsznv8npw5.fsf@charged.uio.no

Trond Myklebust wrote:

>>>>>>" " == David Chow <davidchow@shaolinmicro.com> writes:
>>>>>>            
>>>>>>
>
>     > Even I cat the file, the file seems still using the old cache
>     > on the client, but the server version has changed. Any
>     > possibilities? The mtime and size of the file at the server HAS
>     > changed so why not nfs client refresh_inode() on openning the
>     > file?
>
>That should normally not happen. Are you also updating ctime properly
>on the server when you change the mtime/size?
>
>Cheers,
>  Trond
>  
>
Of course the ctime has changed because the file is edited and saved at 
the server. The problem is it is not close-to-open in this case. I 
notice dir.c has some change in lookup_revalidate(), whats the purpose 
of the change from 2.4.18 to 2.4.19? I have no problem in 2.4.18 .

David


  reply	other threads:[~2002-08-29  9:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-26 15:53 Problems of lookup_revalidate David Chow
2002-08-26 16:10 ` Trond Myklebust
2002-08-27  1:35   ` David Chow
2002-08-27 18:00     ` Trond Myklebust
2002-08-29  9:26       ` David Chow [this message]
2002-08-29  9:31         ` Trond Myklebust
2002-08-29  9:34         ` Trond Myklebust
  -- strict thread matches above, loose matches on Subject: below --
2002-08-29 15:26 Bryan Henderson
2002-08-29 23:19 ` 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=3D6DE8C8.3080601@shaolinmicro.com \
    --to=davidchow@shaolinmicro.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 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.