All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Warren <warren@atmos.washington.edu>
To: nfs@lists.sourceforge.net
Subject: NFS caching bug is back
Date: Thu, 19 Apr 2007 08:43:35 -0700	[thread overview]
Message-ID: <46278E27.8050705@atmos.washington.edu> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1964 bytes --]

A bug that we turned in a while ago is back in the 2.6.20 kernels, only 
worse. I have found it in 2.6.20.6 and 2.6.20.7. It happens with both 
NFS4 and NFS3 mounts. Clients don't see inode changes (delete and 
recreate file):
Setup:
3 systems all running:
Linux enkf1 2.6.20.7 #1 SMP Wed Apr 18 16:23:15 PDT 2007 x86_64 GNU/Linux
File system is xfs. mounted as:
/dev/sda3       /home/enkf      xfs     defaults        0       2
exported as:
(fsid=0,nohide,rw,no_subtree_check,sync,no_root_squash)
NFS mounted as
enkf1:/ /home/enkf   nfs4   rw,proto=tcp,rsize=32768,wsize=32768,hard  0 0
also as
enkf1:/ /home/enkf   nfs   rw,proto=tcp,rsize=8192,wsize=8192,hard  0 0
and
enkf1:/ /home/enkf   nfs   rw,proto=tcp,hard  0 0

Here are the mounts according to the mount command:
enkf1 -
/dev/sda3 on /home/enkf type xfs (rw)

enkf2 -
enkf1:/ on /home/enkf type nfs4 
(rw,proto=tcp,rsize=32768,wsize=32768,hard,addr=128.95.175.220)

enkf3 -
enkf1:/ on /home/enkf type nfs4 
(rw,proto=tcp,rsize=32768,wsize=32768,hard,addr=128.95.175.220)

Here is the sequence in time order. This is even easier to demonstrate 
than the last time:
enkf1:~# echo 2 > /home/enkf/ddd

enkf2:~# cat /home/enkf/ddd
2

enkf3:~# cat /home/enkf/ddd
2

enkf1:~# rm /home/enkf/ddd
enkf1:~# echo 3 > /home/enkf/ddd

enkf2:~# cat /home/enkf/ddd
2

enkf3:~# cat /home/enkf/ddd
2

enkf1:~# ls -i /home/enkf/ddd
10872 /home/enkf/ddd

enkf2:~# ls -i /home/enkf/ddd
10855 /home/enkf/ddd

enkf3:~# ls -i /home/enkf/ddd
10855 /home/enkf/ddd
enkf3:~# touch /home/enkf/ddd
enkf3:~# ls -i /home/enkf/ddd
10872 /home/enkf/ddd

enkf2:~# ls -i /home/enkf/ddd
10855 /home/enkf/ddd



-- 
David Warren 		INTERNET: warren@atmos.washington.edu
(206) 543-0945		Fax: (206) 543-0308
University of Washington
Dept of Atmospheric Sciences, Box 351640
Seattle, WA 98195-1640
-------------------------------------------------------------------------------
DECUS E-PUBS Library Committee representative
SeaLUG DECUS Chair


[-- Attachment #1.2: Type: text/html, Size: 3051 bytes --]

[-- Attachment #2: Type: text/plain, Size: 286 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

[-- Attachment #3: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2007-04-19 15:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-19 15:43 David Warren [this message]
2007-04-19 16:25 ` NFS caching bug is back Bryan O'Sullivan
2007-04-19 18:06   ` David Warren
2007-04-19 18:22     ` Trond Myklebust
2007-04-19 19:31       ` David Warren
2007-04-19 19:36       ` David Warren
2007-04-19 19:52       ` David Warren
2007-04-19 21:29       ` NFS caching bug is back - We think we found it David Warren
2007-04-19 16:36 ` NFS caching bug is back 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=46278E27.8050705@atmos.washington.edu \
    --to=warren@atmos.washington.edu \
    --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.