From: Knut Petersen <Knut_Petersen@t-online.de>
To: linux-kernel@vger.kernel.org
Cc: neilb@cse.unsw.edu.au, trond.myklebust@fys.uio.no,
nfs@lists.sourceforge.net
Subject: [BUG] nfs version 2 broken
Date: Wed, 01 Feb 2006 07:07:45 +0100 [thread overview]
Message-ID: <43E05031.2000107@t-online.de> (raw)
Hi everybody,
The good news is that I finally succeeded to boot over network
using the PXE-bootrom / ip dhcp autoconfig / nfsroot method.
But "ip=dhcp root=/dev/nfs nfsroot=%s" is not the way to go
with recent kernels. This results in a kernel panic caused by
the inability to find root. Things go wrong immediately after
rpc port lookup:
> NFS: Buggy server - nlink == 0!
> nfs_fhget failed
Well, adding ",v3" to the nfsroot parameter helps, forcing the
client not to use the default nfs version 2 but nfs version 3.
All machines use kernel 2.6.15-git7.
cu,
Knut
next reply other threads:[~2006-02-01 6:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 6:07 Knut Petersen [this message]
2006-02-01 6:15 ` [BUG] nfs version 2 broken Trond Myklebust
2006-02-01 6:34 ` Knut Petersen
2006-02-01 6:35 ` Trond Myklebust
2006-02-01 6:46 ` Knut Petersen
2006-02-01 7:13 ` Knut Petersen
2006-02-01 16:41 ` Trond Myklebust
2006-02-01 19:19 ` Knut Petersen
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=43E05031.2000107@t-online.de \
--to=knut_petersen@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox