From: Jakob Oestergaard <jakob@unthought.net>
To: linux-kernel@vger.kernel.org
Subject: NFS-root NFS mouting problem
Date: Mon, 1 Jul 2002 15:14:07 +0200 [thread overview]
Message-ID: <20020701131407.GA19843@unthought.net> (raw)
Hi,
I'm trying to net-boot a system (root NFS) here, but I run into trouble
mounting NFS filesystems *after* the root filesystem has been mounted
(over NFS).
Both server and client are 2.4.18 on i686 - everything works great if I
boot from a disk and mount the home filesystem via. NFS.
Booting the client via. pxelinux, the following happens:
*) Kernel loads, gets IP, ...
*) / is mounted (rw) via NFS
*) Init-scripts start running, brings up eth0, lo, portmapper, syslog,
NFS locking services, all is ok...
*) Init-scripts attempt to mount the home filesystem from the server,
just like it would if booting from the disk. This fails with the
following errors:
--------------------------
Mounting NFS filesystems: exec: Stale NFS handle
mount: Stale NFS handle
exec: Stale NFS handle
touch: creating '/var/lock/subsys/netfs': Stale NFS handle
Mounting other filesystems: exec: Stale NFS handle
dup2: Bad file descriptor
exec: Stale NFS handle
--------------------------
I tried net-booting to single-user mode, which works perfectly well.
Then, mounting *any* NFS filesystem will lock the system with stale NFS
handles again.
The *really* interesting thing is, that after one such failed attempt, I
must re-start the NFS *server*, otherwise the client gets a "Root-NFS
server returned error -13 while mounting /netboot/falcon"... But I
suppose this problem will go away with the first one.
Anything I can try ? Any ideas ? Need more information ?
--
................................................................
: jakob@unthought.net : And I see the elder races, :
:.........................: putrid forms of man :
: Jakob Østergaard : See him rise and claim the earth, :
: OZ9ABN : his downfall is at hand. :
:.........................:............{Konkhra}...............:
reply other threads:[~2002-07-01 13:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020701131407.GA19843@unthought.net \
--to=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.