Edit /etc/rc.d/rc.inet1 . Move the entry for starting rpc.portmap to a
spot that starts it before the system mounts nfs partitions. This was a
problem that was fixed pretty recently with slackware, but wasn't an issue
for 2.0 kernels. NFS 2.2beta40 should be available at
ftp://ftp.mathematik.th-darmstadt.de/pub/linux/okir/dontuse/nfs-server-2.2beta40.tar.gz

I have had little or no trouble with nfs 2.2beta37 on the 2.2 kernels, so
I seriously doubt this is the cause of your problems. I've never seen the
other error b4 (regarding a.out binaries) so have no clue for a course of 
action.

-Donald Thompson

On Sat, 13 Mar 1999, Mark H. Wood wrote:

> I recently upgraded the box that I use for dialout routing from 2.0.29 to 
> 2.2.1.  The box is not totally diskless, but I mount /usr and /home 
> across NFS from another Linux box (kernel 2.1.129, usermode NFS server 
> 2.2beta37).  The router system had no complaints using this approach when 
> running kernel 2.0.  I made sure that I have the latest mount (2.9i).
> 
> After the kernel upgrade, however, I now get stalls and errors when it 
> mounts the NFS volumes:
> 
> Mar 12 20:07:44 woodshed kernel: portmap: RPC call returned error 111  
> Mar 12 20:07:44 woodshed kernel: RPC: task of released request still queued!  
> Mar 12 20:07:44 woodshed kernel: RPC: (task is on xprt_pending)  
> Mar 12 20:07:44 woodshed kernel: portmap: RPC call returned error 111  
> Mar 12 20:07:44 woodshed kernel: RPC: task of released request still queued!  
> Mar 12 20:07:44 woodshed kernel: RPC: (task is on xprt_pending)  
> Mar 12 20:07:44 woodshed kernel: lockd_up: makesock failed, error=-111  
> Mar 12 20:07:44 woodshed kernel: portmap: RPC call returned error 111  
> Mar 12 20:07:44 woodshed kernel: RPC: task of released request still queued!  
> Mar 12 20:07:44 woodshed kernel: RPC: (task is on xprt_pending)  
> Mar 12 20:07:45 woodshed kernel: lockd_up: no pid, 2 users??  
> Mar 12 20:07:45 woodshed kernel: portmap: RPC call returned error 111  
> Mar 12 20:07:45 woodshed kernel: RPC: task of released request still queued!  
> Mar 12 20:07:45 woodshed kernel: RPC: (task is on xprt_pending)  
> Mar 12 20:07:45 woodshed kernel: portmap: RPC call returned error 111  
> Mar 12 20:07:45 woodshed kernel: RPC: task of released request still queued!  
> Mar 12 20:07:45 woodshed kernel: RPC: (task is on xprt_pending)  
> Mar 12 20:07:45 woodshed kernel: portmap: RPC call returned error 111  
> Mar 12 20:07:45 woodshed kernel: RPC: task of released request still queued!  
> Mar 12 20:07:45 woodshed kernel: RPC: (task is on xprt_pending)  
> Mar 12 20:07:49 woodshed kernel: lockd: failed to monitor 192.168.1.2  
> 
> After all that, NFS seems to work pretty well anyway (but read on).  Any 
> ideas?  I can't even find a '*lockd*' executable -- where is this last 
> one coming from?
> 
> Also I now get errors when trying to run a.out executables fetched via NFS:
> 
>       N_TXTOFF < BLOCK_SIZE. Please convert binary.
> 
> I found some earlier messages about this that suggested problems with 
> large NFS transfer sizes, but cutting back to 1024 didn't help.
> 
> I know, I know -- I should rebuild all the a.out commands as ELF, and 
> I've done those that I have been able to find.  (My systems are Slackware 
> 1.2 plus five years of piecemeal upgrades -- tell me you *know* that 
> pasting 3.5 over them won't break a basketful of things I've set up in 
> the interval.)  Some of them are proving hard to find.
> 
> Please don't tell me to upgrade the server to beta40 unless you also tell 
> me where to find it.  The site listed in CHANGES only has beta37, the 
> version I'm running now.
> 
> aTdHvAaNnKcSe
> 
> -- 
> Mark H. Wood, radical centrist                             [EMAIL PROTECTED]
> Charlie, put down that Glitter Glue -- it's time to show the audience
> some content!
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to [EMAIL PROTECTED]
> 
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]

Reply via email to