From: Lukas Razik <linux@razik.name>
To: Jim Rees <rees@umich.edu>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [BUG?] Maybe NFS bug since 2.6.37 on SPARC64
Date: Fri, 4 Nov 2011 00:59:59 +0000 (GMT) [thread overview]
Message-ID: <1320368399.51438.YahooMailNeo@web24715.mail.ird.yahoo.com> (raw)
In-Reply-To: <20111103235922.GA12527@umich.edu>
> I suspect some kind of timing problem, where the network interface hasn't
> come up yet at the time the portmap request is made. What does your nfsroot
> kernel option look like? What happens if you add ",port=2049" to the
> end of
> your nfsroot kernel option?
That's my kernel line (and it's exactly the same for all kernel versions I used):
root=/dev/nfs rw nfsroot=137.226.167.241:/srv/nfs/cluster2 ip=137.226.167.242::137.226.167.225:255.255.255.224:cluster2:eth0:off nfsrootdebug
(I know that nfsrootdebug isn't available in older kernels but it doesn't matter...)
With ",port=2049" I get this from linux-2.6.29.4:
[ 252.932407] IP-Config: Complete:
[ 252.932476] device=eth0, addr=137.226.167.242, mask=255.255.255.224, gw=137.226.167.225,
[ 252.932680] host=cluster2, domain=, nis-domain=(none),
[ 252.932794] bootserver=255.255.255.255, rootserver=137.226.167.241, rootpath=
[ 252.933230] Root-NFS: nfsroot=/srv/nfs/cluster2,port=2049
[ 252.933523] NFS: nfs mount opts='udp,port=2049,nolock,addr=137.226.167.241'
[ 252.933583] NFS: parsing nfs mount option 'udp'
[ 252.933621] NFS: parsing nfs mount option 'port=2049'
[ 252.933675] NFS: parsing nfs mount option 'nolock'
[ 252.933722] NFS: parsing nfs mount option 'addr=137.226.167.241'
[ 252.933787] NFS: MNTPATH: '/srv/nfs/cluster2'
[ 252.933823] NFS: sending MNT request for 137.226.167.241:/srv/nfs/cluster2
[ 254.038874] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[ 254.059251] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 288.023684] NFS: failed to create MNT RPC client, status=-60
[ 288.023793] NFS: unable to mount server 137.226.167.241, error -60
[ 288.023929] VFS: Unable to mount root fs via NFS, trying floppy.
[ 288.024092] VFS: Insert root floppy and press ENTER
So the result is the same as before...
In the past I also tried higher "timeo" and I think higher "retrans" values but also without a positive effect...
next prev parent reply other threads:[~2011-11-04 1:00 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 19:43 [BUG?] Maybe NFS bug since 2.6.37 on SPARC64 Lukas Razik
2011-11-03 20:54 ` Trond Myklebust
2011-11-03 21:10 ` Chuck Lever
2011-11-03 21:11 ` Jim Rees
2011-11-03 21:16 ` Chuck Lever
2011-11-03 21:37 ` Lukas Razik
2011-11-03 21:51 ` Chuck Lever
2011-11-03 23:09 ` Lukas Razik
2011-11-03 23:59 ` Jim Rees
2011-11-04 0:59 ` Lukas Razik [this message]
2011-11-04 1:06 ` Chuck Lever
2011-11-04 1:33 ` Lukas Razik
2011-11-04 9:44 ` Lukas Razik
2011-11-04 13:20 ` Jim Rees
2011-11-04 14:01 ` Chuck Lever
2011-11-04 14:09 ` Myklebust, Trond
2011-11-04 14:24 ` J. Bruce Fields
2011-11-04 14:46 ` Jim Rees
2011-11-04 15:02 ` Lukas Razik
2011-11-04 15:18 ` Myklebust, Trond
2011-11-04 15:46 ` Lukas Razik
2011-11-04 22:55 ` Chuck Lever
2011-11-04 23:17 ` Lukas Razik
2011-11-04 13:54 ` Chuck Lever
2011-11-04 14:57 ` Lukas Razik
2011-11-04 16:56 ` Lukas Razik
2011-11-04 17:55 ` Lukas Razik
2011-11-04 23:15 ` NFSROOT mount fails on SPARC after 2.6.37 Chuck Lever
2011-11-05 2:03 ` David Miller
2011-11-05 2:38 ` Trond Myklebust
2011-11-04 23:40 ` [BUG?] Maybe NFS bug since 2.6.37 on SPARC64 Lukas Razik
2011-11-05 1:19 ` Trond Myklebust
2011-11-05 1:52 ` Lukas Razik
2011-11-05 2:14 ` Lukas Razik
2011-11-05 2:30 ` Trond Myklebust
2011-11-05 2:31 ` Trond Myklebust
2011-11-05 2:31 ` Trond Myklebust
2011-11-05 3:51 ` Lukas Razik
2011-11-05 13:05 ` Jim Rees
2011-11-12 11:35 ` Lukas Razik
2011-11-12 18:49 ` Jim Rees
2011-11-12 21:06 ` Chuck Lever
2011-11-13 1:03 ` Lukas Razik
2011-11-13 19:32 ` Chuck Lever
2011-11-13 21:28 ` Lukas Razik
2011-11-13 22:19 ` Lukas Razik
2011-11-14 15:31 ` Chuck Lever
2011-11-03 21:18 ` Lukas Razik
2011-11-03 21:38 ` Jim Rees
2011-11-03 21:58 ` Lukas Razik
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=1320368399.51438.YahooMailNeo@web24715.mail.ird.yahoo.com \
--to=linux@razik.name \
--cc=Trond.Myklebust@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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