All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Banks <gnb@melbourne.sgi.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Olaf Kirch <okir@suse.de>, nfs@lists.sourceforge.net
Subject: Re: Marking inodes as stale can be wrong
Date: Fri, 30 Apr 2004 11:51:40 +1000	[thread overview]
Message-ID: <4091B12C.FBB1FF34@melbourne.sgi.com> (raw)
In-Reply-To: 1083285820.14910.77.camel@lade.trondhjem.org

Trond Myklebust wrote:
> 
> Note for instance that the error NFS3ERR_JUKEBOX is not listed as a
> return value for any of the procedures: I'm sure that it would come as a
> surprise to most server implementors if you were to disallow its use
> solely on those grounds.

Oh indeed ;-)  My next server patch does precisely that.

Greg.
-- 
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-04-30  1:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29 14:40 Marking inodes as stale can be wrong Olaf Kirch
2004-04-29 16:44 ` Trond Myklebust
2004-04-29 16:58   ` Olaf Kirch
2004-04-29 17:09     ` Trond Myklebust
2004-04-29 21:28       ` Olaf Kirch
2004-04-29 23:50       ` Greg Banks
2004-04-30  0:43         ` Trond Myklebust
2004-04-30  1:51           ` Greg Banks [this message]
2004-04-30  8:34             ` Olaf Kirch
2004-04-30  8:47               ` Greg Banks
2004-04-30  8:58                 ` Olaf Kirch
2004-04-29 17:21 ` 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=4091B12C.FBB1FF34@melbourne.sgi.com \
    --to=gnb@melbourne.sgi.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=okir@suse.de \
    --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.