From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Lukas Razik <linux@razik.name>
Cc: Chuck Lever <chuck.lever@oracle.com>, Jim Rees <rees@umich.edu>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [BUG?] Maybe NFS bug since 2.6.37 on SPARC64
Date: Fri, 04 Nov 2011 22:30:44 -0400 [thread overview]
Message-ID: <1320460244.2750.19.camel@lade.trondhjem.org> (raw)
In-Reply-To: <1320459252.59518.YahooMailNeo@web24716.mail.ird.yahoo.com>
On Sat, 2011-11-05 at 02:14 +0000, Lukas Razik wrote:
> ***IMPORTANT HINT***
>
> In the test belowI've tried to ping the NFS client (cluster2) as soon as I've got the
>
> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> message.
>
>
> And at first I've got no answers from the client. But 10-20sec later I've got pongs back.
> So the NIC comes up some seconds later than the message "link becomes ready" is shown...
> In the case of 'mountproto=tcp' it comes up after the kernel panic. So that's much too late.
>
So, once again...
What kind of switch is this client connected to, and how is that switch
configured?
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2011-11-05 2:32 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
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 [this message]
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=1320460244.2750.19.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux@razik.name \
--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