public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Krogh <jesper-Q2TZfHgGEy4@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: Client cache updates missing? (2.6.31.5)
Date: Sun, 29 Nov 2009 09:24:18 +0100	[thread overview]
Message-ID: <4B122FB2.7040505@krogh.cc> (raw)

Hi.

I'm seeing some random odd behaviour on my NFS clients. It is
not directly reproducible, but I have had users telling me about, but
until you hit stuff like this yourself .. you almost dont believe it.

jk@bach:~$ ssh nfsserver ls -ltrah | grep blast-2.out
-rw-rw-r--   1 jk jk 552K 2009-11-29 09:10 blast-2.out
jk@bach:~$ ls -tlrha  | grep blast-2.out
jk@bach:~$ date
Sun Nov 29 09:17:14 CET 2009
jk@bach:~$ stat blast-2.out
  File: `blast-2.out'
  Size: 564283    	Blocks: 1112       IO Block: 1048576 regular file
Device: 18h/24d	Inode: 139405089   Links: 1
Access: (0664/-rw-rw-r--)  Uid: ( 1000/      jk)   Gid: ( 1000/      jk)
Access: 2009-11-29 09:07:34.000000000 +0100
Modify: 2009-11-29 09:10:27.000000000 +0100
Change: 2009-11-29 09:10:27.0000

So.. the file has been present for 7 minutes on the NFS-server (and any
client doing a fresh mount) but the client I'm sitting on is not having
the file in the directory listing, but if I explicitly ask for it.. its
there.

Wether or not it has anything to do. The file has been written to the
NFS-server from another NFS-client. The server is running 2.6.31.5 and
the client that above was run on is 2.6.24-24 (Ubuntu Jaunty), the
client that wrote the file was running 2.6.29.1.

Jesper
-- 
Jesper

             reply	other threads:[~2009-11-29  8:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-29  8:24 Jesper Krogh [this message]
     [not found] ` <4B122FB2.7040505-Q2TZfHgGEy4@public.gmane.org>
2009-11-30 18:26   ` Client cache updates missing? (2.6.31.5) J. Bruce Fields
2009-11-30 18:30     ` Jesper Krogh
     [not found]       ` <4B140F5F.6050107-Q2TZfHgGEy4@public.gmane.org>
2009-11-30 18:40         ` J. Bruce Fields
2009-11-30 18:53           ` 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=4B122FB2.7040505@krogh.cc \
    --to=jesper-q2tzfhggey4@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox