From: Spencer Shepler <spencer.shepler@sun.com>
To: Frank van Maarseveen <frankvm@frankvm.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Linux NFS mailing list <nfs@lists.sourceforge.net>
Subject: Re: Re: EJUKEBOX and nfs3_proc_read()/nfs3_proc_write()
Date: Thu, 27 Jan 2005 22:15:29 -0800 [thread overview]
Message-ID: <20050128061529.GA944944@jurassic.eng.sun.com> (raw)
In-Reply-To: <20050127233831.GA24817@janus>
On Fri, Frank van Maarseveen wrote:
> On Thu, Jan 27, 2005 at 03:19:57PM -0800, Trond Myklebust wrote:
> > to den 27.01.2005 Klokka 23:59 (+0100) skreiv Frank van Maarseveen:
> > > I think that the EJUKEBOX wrapper in fs/nfs/nfs3proc.c is not necessary
> > > for nfs3_proc_read() and nfs3_proc_write().
> > >
> > > Can you confirm this?
> >
> > Why do you believe that?
>
> Because you have to open a file first. Well, as you said NFS is stateless
> so my guess is that the final lookup would return EJUKEBOX rather
> than any I/O on the file-handle. It seems unrealistic to me for a file to
> be archived _during_ I/O.
>
> Sure the protocol has the possibility to return EJUKEBOX in the middle
> of file I/O but does it make sense?
Yes. It makes sense. There are HSM solutions that keep the first
portion of the file on disk to be provided to things like the file
command. If the whole file is read, then subsequent READ requests
may receive EJUKEBOX.
>
> BTW, I didn't see EJUKEBOX handling in NFSv4.
NFS4ERR_DELAY
Spencer
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2005-01-28 6:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 22:59 EJUKEBOX and nfs3_proc_read()/nfs3_proc_write() Frank van Maarseveen
2005-01-27 23:19 ` Trond Myklebust
2005-01-27 23:38 ` Frank van Maarseveen
2005-01-28 0:43 ` Trond Myklebust
2005-01-28 6:15 ` Spencer Shepler [this message]
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=20050128061529.GA944944@jurassic.eng.sun.com \
--to=spencer.shepler@sun.com \
--cc=frankvm@frankvm.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 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.