Linux NFS development
 help / color / mirror / Atom feed
From: David Warren <warren@atmos.washington.edu>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Bryan O'Sullivan <bos@serpentine.com>, nfs@lists.sourceforge.net
Subject: Re: NFS caching bug is back - We think we found it
Date: Thu, 19 Apr 2007 14:29:44 -0700	[thread overview]
Message-ID: <4627DF48.8080609@atmos.washington.edu> (raw)
In-Reply-To: <1177006975.6623.8.camel@heimdal.trondhjem.org>


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

After more testing, we think we have the answer. It looks like the only 
servers that exhibit this problem are ones that have gfs disks attached. 
Systems with identical kernels except for no gfs, gfs2 or dlm modules do 
not seem to do this. So, something in the gfs modules must be trashing 
some kernel structure that the nfs server uses, even though this is not 
a gfs file system.

Trond Myklebust wrote:
> On Thu, 2007-04-19 at 11:06 -0700, David Warren wrote:
>
>   
>> I don't know that much about the inner workings of the NFS protocol,
>> but considering that the inode has been removed and replaced by a new
>> one shouldn't all the return values from the access request be 0? It
>> seems odd that read, modify, extend and execute are allowed for a
>> nonexistent object.
>>     
>
> The filehandle should normally be invalidated and any attempt by the
> client to use it should result in an ESTALE error. The exception would
> be if a hard link to the file still exists somewhere on the filesystem
> (which didn't seem to be the case in your test).
>
> Irrespective of whether or not the file still exists somewhere else, the
> mtime on the parent directory _will_ change when you unlink the file.
> The client is supposed to pick up on this and re-issue a LOOKUP and/or
> OPEN for the file, at which point the server should reply with an ENOENT
> or with the new file and its filehandle in something like your testcase.
>
> My immediate advice would be to take the whole filesystem offline and
> fsck it just in order to be sure that there are no corruption that might
> be confusing the NFS server.
>
> Cheers
>   Trond
>   

-- 
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: 2469 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

  parent reply	other threads:[~2007-04-19 21:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-19 15:43 NFS caching bug is back David Warren
2007-04-19 16:25 ` 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       ` David Warren [this message]
2007-04-19 16:36 ` 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=4627DF48.8080609@atmos.washington.edu \
    --to=warren@atmos.washington.edu \
    --cc=bos@serpentine.com \
    --cc=nfs@lists.sourceforge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox