From: Lukas Razik <linux@razik.name>
To: Jim Rees <rees@umich.edu>, Chuck Lever <chuck.lever@oracle.com>
Cc: 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 15:46:42 +0000 (GMT) [thread overview]
Message-ID: <1320421602.96030.YahooMailNeo@web24707.mail.ird.yahoo.com> (raw)
In-Reply-To: <20111104144617.GB911@umich.edu>
> > As for a fix... we're trying to move away from udp transport
> anyway. Maybe
> > someone should figure out a way to get it to work with tcp? I have zero
> > experience with nfs over udp, at least on linux. Just for fun, have you
> > tried tcp transport (proto=tcp)?
>
> TCP is a real problem in this environment, because it deals poorly with
> NIC initialization timing issues. UDP is still the best approach (as long
> as it is retransmitting appropriately). To support TCP, ultimately what
> we need to do is to introduce serialization to make the kernel wait for
> the NIC to become ready before attempting network activity.
>
> Agreed, but we're grasping at straws here, and this guy just wants it to
> work. It's something to try.
I've tried that but "proto=tcp" is no way to change the protocol in linux-2.6.39.4.
It uses the udp protocol and in "Documentation/filesystems/nfs/nfsroot.txt" there's no "proto" option (or something similar).
[11140.866623] IP-Config: Complete:
[11140.866692] device=eth0, addr=137.226.167.242, mask=255.255.255.224, gw=137.226.167.225,
[11140.866895] host=cluster2, domain=, nis-domain=(none),
[11140.867008] bootserver=255.255.255.255, rootserver=137.226.167.241, rootpath=
[11140.867431] Root-NFS: nfsroot=/srv/nfs/cluster2,proto=tcp,retrans=10,timeo=60
[11140.867728] NFS: nfs mount opts='udp,proto=tcp,retrans=10,timeo=60,nolock,addr=137.226.167.241'
[11140.867797] NFS: parsing nfs mount option 'udp'
[11140.867836] NFS: parsing nfs mount option 'proto=tcp'
[11140.867895] NFS: parsing nfs mount option 'retrans=10'
[11140.867946] NFS: parsing nfs mount option 'timeo=60'
[11140.867996] NFS: parsing nfs mount option 'nolock'
[11140.868043] NFS: parsing nfs mount option 'addr=137.226.167.241'
[11140.868106] NFS: MNTPATH: '/srv/nfs/cluster2'
[11140.868142] NFS: sending MNT request for 137.226.167.241:/srv/nfs/cluster2
[11141.912761] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx
[11141.933177] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[11143.873095] NFS: failed to create MNT RPC client, status=-65
[11143.873205] NFS: unable to mount server 137.226.167.241, error -65
[11143.873339] VFS: Unable to mount root fs via NFS, trying floppy.
[11143.873494] VFS: Insert root floppy and press ENTER
Now I'll try the other workaround idea: netboot from tftp (to bring eth0 up) and subsequent nfsroot mount.
Therefore I need a customized (and rather small) kernel...
Regards,
Lukas
next prev parent reply other threads:[~2011-11-04 15:46 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
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 [this message]
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=1320421602.96030.YahooMailNeo@web24707.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