lkml.org 
[lkml]   [1997]   [Oct]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subject2.1.60 NFS probs...
Hi,

I'm experiencing some difficulty with NFS-root in 2.1.60 (+Bill Hawes
nfs_client60-patch):

On booting the client, the root partition sometimes fails to mount.
This is rather an odd start, as the server and client are the only
two participants on a thinnet. It almost always boots without
problem the second time, though:

-- failure
er... I can't reproduce this one, and unsurprisingly, I have no
logs from the failures :)

-- success!
ne.c:v1.10 9/23/94 Donald Becker (becker@cesdis.gsfc.nasa.gov)
NE*000 ethercard probe at 0x300: 00 00 e8 2b 76 73
eth0: NE2000 found at 0x300, using IRQ 4.
Looking up port of RPC 100003/2 on 163.1.138.129
Looking up port of RPC 100005/1 on 163.1.138.129
VFS: Mounted root (nfs filesystem).

Once root is mounted, various daemons fire off, and then the attempt
to mount /home produces:
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)

Although this may be due to the RH startup scripts producing a broken
routing table. After this everything's OK and I can log in, fix the
routes and fire up Quake, ftp, telnet, ssh, etc...

However, the following rather painless message can be repeatably
provoked by ( cd /usr/src/linux ; make menuconfig ), among other
things:
NFS: invalidating pending RPC requests

Once this has happened, that process hangs, and any logins on other
consoles fail also. Stopping and starting the NFS server fixes this
and ps shows a
/bin/sh scripts/Menuconfig arch/i386/config.in
in the "D" state and nothing else of particular interest.
"ps l" claims that every process but itself is in "end" which I find
vaguely confusing.

It looks to me as if the machine is hanging processes in exactly the
same places as it would previously have corrupted files.

Attempts to shutdown and reboot fill the screen (and logs) with
RPC: sendmsg returned error 101
and occasionally
RPC: server 163.1.138.129 not responding, still trying

101 == ENETUNREACH

so obviously I've done something daft with the routing table...


-- client fstab
163.1.138.129:/tftpboot/163.1.138.123 / nfs defaults 1 1
163.1.138.129:/home /home nfs defaults 1 2
/dev/fd0 /mnt/floppy ext2 noauto 0 0
none /proc proc defaults 0 0

-- server exports
/tftpboot/163.1.138.123 163.1.138.123(rw,no_root_squash)
/home 163.1.138.123(ro,no_root_squash)

More info as required...

Matthew.

--
Matthew Kirkwood | Mail: matthew.kirkwood@lmh.ox.ac.uk
LMH JCR, | Web: http://www-jcr.lmh.ox.ac.uk/~weejock/
Oxford OX2 6QA, | PGP: finger weejock@ferret.lmh.ox.ac.uk
England. |

\
 
 \ /
  Last update: 2005-03-22 13:40    [from the cache]
©2003-2011 Jasper Spaans