From: Chuck Lever <chuck.lever@oracle.com>
To: Reiter Rafael <rafael.reiter@ims.co.at>
Cc: linux-rdma@vger.kernel.org,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Kernel oops/panic with NFS over RDMA mount after disrupted Infiniband connection
Date: Thu, 27 Mar 2014 08:59:06 -0700 [thread overview]
Message-ID: <B7D4A29C-5E1F-4B6C-A8FC-C46D8DF6A87D@oracle.com> (raw)
In-Reply-To: <lh0le0$u5$1@ger.gmane.org>
Hi-
On Mar 27, 2014, at 12:53 AM, Reiter Rafael <rafael.reiter@ims.co.at> wrote:
> On 03/26/2014 07:15 PM, Chuck Lever wrote:
>>
>> Hi Rafael-
>>
>> I’ll take a look. Can you report your HCA and how you reproduce this issue?
>
> The HCA is Mellanox Technologies MT26428.
>
> Reproduction:
> 1) Mount a directory via NFS/RDMA
> mount -t nfs -o port=20049,rdma,vers=4.0,timeo=900 172.16.100.2:/ /mnt/
> 2) Pull the Infiniband cable or use ibportstate to disrupt the Infiniband connection
> 3) ls /mnt
> 4) wait 5-30 seconds
Thanks for the information.
I have that HCA, but I won’t have access to my test systems for a week (traveling). So can you try this:
# rpcdebug -m rpc -s trans
then reproduce (starting with step 1 above). Some debugging output will appear at the tail of /var/log/messages. Copy it to this thread.
>
>>
>> Do you (or does anyone) know whether OpenSuSE uses the stock upstream providers, or has any of OFED been applied to this kernel?
>
> My first post was misleading -- I use the vanilla 3.10.17 kernel, and the error occurs with and without Mellanox OFED. The above report
> references the vanilla kernel.
>
> Rafael
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
next prev parent reply other threads:[~2014-03-27 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 13:20 Kernel oops/panic with NFS over RDMA mount after disrupted Infiniband connection rafael.reiter
2014-03-26 18:15 ` Chuck Lever
2014-03-27 7:53 ` Reiter Rafael
2014-03-27 15:59 ` Chuck Lever [this message]
2014-03-28 9:42 ` Senn Klemens
2014-03-28 22:30 ` Chuck Lever
2014-03-28 23:06 ` sagi grimberg
2014-03-29 0:05 ` Chuck Lever
2014-03-29 0:52 ` sagi grimberg
2014-04-04 15:20 ` Chuck Lever
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=B7D4A29C-5E1F-4B6C-A8FC-C46D8DF6A87D@oracle.com \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=rafael.reiter@ims.co.at \
/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;
as well as URLs for NNTP newsgroup(s).