From: Andrew Walrond <andrew@walrond.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.bk no longer boots from NFS root after bk pull this morning
Date: Wed, 15 Jan 2003 11:59:48 +0000 [thread overview]
Message-ID: <3E254D34.9030100@walrond.org> (raw)
In-Reply-To: shsd6mz5zca.fsf@charged.uio.no
Trond Myklebust wrote:
>
> > NFS: server cheating in read reply: count 4096 > recvd 1000
>
> Did this start with the 2.5.58 client? What is the server running?
>
*** 2.5.57 is fine;
Sending DHCP requests ., OK
IP-Config: Got DHCP answer from 10.0.0.1, my address is 10.0.0.103
IP-Config: Complete:
device=eth0, addr=10.0.0.103, mask=255.255.0.0, gw=10.0.0.1,
host=hal3.office, domain=office, nis-domain=(none),
bootserver=10.0.0.1, rootserver=10.0.0.1,
rootpath=/eboot/slash/hal.office
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 10.0.0.1
Looking up port of RPC 100005/1 on 10.0.0.1
VFS: Mounted root (nfs filesystem).
*** 2.5.58 is fine (with your patches so it boots)
Sending DHCP requests ., OK
IP-Config: Got DHCP answer from 10.0.0.1, my address is 10.0.0.103
IP-Config: Complete:
device=eth0, addr=10.0.0.103, mask=255.255.0.0, gw=10.0.0.1,
host=hal3.office, domain=office, nis-domain=(none),
bootserver=10.0.0.1, rootserver=10.0.0.1,
rootpath=/eboot/slash/hal.office
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 10.0.0.1
Looking up port of RPC 100005/1 on 10.0.0.1
VFS: Mounted root (nfs filesystem).
*** 2.5 BK (same as yesterday)
Sending DHCP requests ., OK
IP-Config: Got DHCP answer from 10.0.0.1, my address is 10.0.0.103
IP-Config: Complete:
device=eth0, addr=10.0.0.103, mask=255.255.0.0, gw=10.0.0.1,
host=hal3.office, domain=office, nis-domain=(none),
bootserver=10.0.0.1, rootserver=10.0.0.1,
rootpath=/eboot/slash/hal.office
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 10.0.0.1
Looking up port of RPC 100005/1 on 10.0.0.1
VFS: Mounted root (nfs filesystem).
*** Hmmm. No strange message this time
Sorry this isn't more useful. Anything else I can do?
prev parent reply other threads:[~2003-01-15 11:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 10:03 2.5.bk no longer boots from NFS root after bk pull this morning Andrew Walrond
2003-01-14 10:09 ` William Lee Irwin III
2003-01-14 10:30 ` Andrew Walrond
2003-01-14 11:24 ` William Lee Irwin III
2003-01-14 11:25 ` William Lee Irwin III
2003-01-14 15:32 ` Trond Myklebust
2003-01-14 16:24 ` Andrew Walrond
2003-01-14 19:02 ` Trond Myklebust
2003-01-15 10:22 ` Andrew Walrond
2003-01-15 11:59 ` Andrew Walrond [this message]
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=3E254D34.9030100@walrond.org \
--to=andrew@walrond.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.