Messages in this thread | | | Date | Wed, 18 Mar 1998 16:41:00 -0500 (EST) | From | <> | Subject | Re: NFS client error messages in 2.1.90pre3 |
| |
Yea.. I've got a single disk linux running .87 (now .90) and it's doing this too.. I hope to find a solution soon.. This disk needs to be in the clients hands friday afternoon.. :)
On Wed, 18 Mar 1998, Lance Kinley wrote:
> > I'm getting the following messages when booting up, during remote > filesystem mounting: > > portmap: RPC call returned error 111 > RPC: task of released request still queued! > RPC: (task is on xprt_pending) > portmap: RPC call returned error 111 > RPC: task of released request still queued! > RPC: (task is on xprt_pending) > lockd_up: makesock failed, error=-111 > portmap: RPC call returned error 111 > RPC: task of released request still queued! > RPC: (task is on xprt_pending) > lockd_up: no pid, 2 users?? > portmap: RPC call returned error 111 > RPC: task of released request still queued! > RPC: (task is on xprt_pending) > portmap: RPC call returned error 111 > RPC: task of released request still queued! > RPC: (task is on xprt_pending) > lockd_up: makesock failed, error=-111 > portmap: RPC call returned error 111 > RPC: task of released request still queued! > RPC: (task is on xprt_pending) > > Then everything works fine... I can use the NFS drives just fine. I also > get a lockd_down: nothing to do! message when unmounting. > > It is mounting a couple drives from a Linux 2.0.33 box. Saw these > messages in both pre2 and pre3. Dunno about other versions, 90pre2 was my > first 2.1.x kernel since 2.1.7 > > Bill Hawes, any ideas? > > -Lance > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.rutgers.edu >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |