All of lore.kernel.org
 help / color / mirror / Atom feed
* 2.4.20 NFS / EJUKEBOX problem
@ 2003-09-17 21:21 Paul N
  2003-09-17 22:38 ` Trond Myklebust
  0 siblings, 1 reply; 2+ messages in thread
From: Paul N @ 2003-09-17 21:21 UTC (permalink / raw)
  To: linux-kernel

Hi,
I'm seeing a weird problem with NFSv3's EJUKEBOX when
mounting a irix machine running DMF (software for managing offline/tape
copies of files).    When an NFS read request is made for an 'offline' file
it causes other write requests to stall until the 'offline'  file is 
unmigrated to
disk and the read can resume. 
 From looking at tcpdump it seems that the write requests proceed until
an EJUKEBOX msg from the read is returned from the server.  At that point
all write requests are stuck behind the  jukeboxed read. 

Could someone please give me some information on this?

Thanks
Paul



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: 2.4.20 NFS / EJUKEBOX problem
  2003-09-17 21:21 2.4.20 NFS / EJUKEBOX problem Paul N
@ 2003-09-17 22:38 ` Trond Myklebust
  0 siblings, 0 replies; 2+ messages in thread
From: Trond Myklebust @ 2003-09-17 22:38 UTC (permalink / raw)
  To: Paul N; +Cc: linux-kernel

>>>>> " " == Paul N <Paul> writes:

     > Hi, I'm seeing a weird problem with NFSv3's EJUKEBOX when
     > mounting a irix machine running DMF (software for managing
     > offline/tape copies of files).  When an NFS read request is
     > made for an 'offline' file it causes other write requests to
     > stall until the 'offline' file is unmigrated to

     > disk and the read can resume. From looking at tcpdump it seems
     > that the write requests proceed until

     > an EJUKEBOX msg from the read is returned from the server.  At
     > that point all write requests are stuck behind the jukeboxed
     > read. Could someone please give me some information on this?

The writes are probably waiting in 'nfs_try_to_free_pages()' because
you are hitting the hard limit on outstanding read/write requests.
The NFS code is not allowed to allocate more than MAX_REQUEST_HARD
requests per mountpoint at any time since there is otherwise no way
for the VM to notify us in case of resource starvation.

Cheers,
  Trond

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-09-17 22:38 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-09-17 21:21 2.4.20 NFS / EJUKEBOX problem Paul N
2003-09-17 22:38 ` Trond Myklebust

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.