From: Per Nystrom <centaur@netmagic.net>
To: linux-kernel@vger.kernel.org
Subject: NFS serving Solaris Jumpstart clients
Date: Fri, 20 Feb 2004 17:36:21 -0800 [thread overview]
Message-ID: <1077327381.3712.45.camel@spike> (raw)
[-- Attachment #1: Type: text/plain, Size: 2049 bytes --]
Hi,
I'm trying to use my Linux laptop to serve Solaris Jumpstarts. The long
and short of it is, kernel 2.4.19 serves NFS to Jumpstart clients just
fine, but after that release something changed. With subsequent
releases (including 2.6.3), the Solaris Jumpstart client just hangs
after mounting the miniroot. It's still ping-able, but it doesn't go
any further. If it's any help, here are the last few lines of tcpdump
output up to the point where the client hangs:
16:46:48.456226 10.42.42.100.nfs > 10.42.42.241.2876172689: reply ok 236
lookup
[|nfs] (DF)
16:46:48.456441 10.42.42.241.2876172690 > 10.42.42.100.nfs: 100 access
[|nfs] (DF)
16:46:48.456471 10.42.42.100.nfs > 10.42.42.241.2876172690: reply ok 120
access
c 0000 (DF)
16:46:48.456755 10.42.42.241.2876172691 > 10.42.42.100.nfs: 100 lookup
[|nfs] (DF)
16:46:48.456782 10.42.42.100.nfs > 10.42.42.241.2876172691: reply ok 236
lookup
[|nfs] (DF)
16:46:48.457110 10.42.42.241.2876172692 > 10.42.42.100.nfs: 100 remove
[|nfs] (DF)
16:46:48.457135 10.42.42.100.nfs > 10.42.42.241.2876172692: reply ok 120
remove
ERROR: Read-only file system (DF)
16:46:48.457445 10.42.42.241.2876172693 > 10.42.42.100.nfs: 100 lookup
[|nfs] (DF)
16:46:48.457475 10.42.42.100.nfs > 10.42.42.241.2876172693: reply ok 236
lookup
[|nfs] (DF)
16:46:48.457695 10.42.42.241.2876172694 > 10.42.42.100.nfs: 132 link
[|nfs] (DF)16:46:48.457718 10.42.42.100.nfs > 10.42.42.241.2876172694:
reply ok 124 link ERROR: Read-only file system (DF)
16:46:48.457946 10.42.42.241.2876172695 > 10.42.42.100.nfs: 104 lookup
[|nfs] (DF)
16:46:48.457977 10.42.42.100.nfs > 10.42.42.241.2876172695: reply ok 236
lookup
[|nfs] (DF)
Note -- the read only file system errors also show up during a
successful run using kernel 2.4.19.
Any help is greatly appreciated -- I don't want to have to dual-boot
Solaris x86 just so I can serve Jumpstarts in the field (for that
matter, I'm not convinced Solaris x86 has the drivers to support my
laptop anyway).
Thanks,
Per Nystrom
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-02-21 1:36 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=1077327381.3712.45.camel@spike \
--to=centaur@netmagic.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pnystrom@netmagic.net \
/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