From: Haakon Riiser <haakon.riiser@fys.uio.no>
Subject: Re: read(2) hangs on the client side
Date: Sun, 15 May 2005 08:21:03 +0200
Message-ID: <20050515062103.GA482@fox>
References: <20050508113343.GA629@fox> <1115556864.11308.1.camel@lade.trondhjem.org> <20050508132127.GA1744@fox> <1115560765.11308.6.camel@lade.trondhjem.org> <20050508143754.GA492@fox> <1115635107.24625.0.camel@lade.trondhjem.org> <20050509141339.GA3216@fox> <1115821422.13483.0.camel@lade.trondhjem.org> <20050514223904.GA580@fox> <1116113888.14297.27.camel@lade.trondhjem.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: nfs@lists.sourceforge.net
To: Trond Myklebust <trond.myklebust@fys.uio.no>
In-Reply-To: <1116113888.14297.27.camel@lade.trondhjem.org>
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

Trond,

> Why didn't you try the NFSv3 RFC? 8-)
> 
>    NFS3ERR_JUKEBOX
>        The server initiated the request, but was not able to
>        complete it in a timely fashion. The client should wait
>        and then try the request with a new RPC transaction ID.
>        For example, this error should be returned from a server
>        that supports hierarchical storage and receives a request
>        to process a file that has been migrated. In this case,
>        the server should start the immigration process and
>        respond to client with this error.
> 
> In other words, this is an error used by the server to say "I'm busy,
> and cannot retrieve the data you want. Please try again later".
> 
> Are you absolutely sure that you managed to disable oplocks on the samba
> server? 'cos this is the error an NFS server will usually return when it
> is waiting for the samba server (or an NFSv4 server) to break the lease
> on a file so that it can be opened.

I did set 'kernel oplocks = no' globally and restarted Samba, but I
didn't look for locked files with smbstatus.  I'll try again and
investigate a little more this time.  In the meantime, here's what
smbstatus shows:

Locked files:
Pid    DenyMode   Access   R/W     Oplock           Name
--------------------------------------------------------
32475  DENY_NONE  0x20089  RDONLY  EXCLUSIVE+BATCH foo Sun May 15 08:13:23 2005

This lock goes on and off all the time, which probably explains why
this error doesn't happen every single time I try to open the file.
But why does ERR_JUKEBOX cause the client to hang?  This lock _is_
soon released, so shouldn't NFS wake up once that happens?

-- 
 Haakon


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs