From: "Rupert Dance" <rsdance@soft-forge.com>
To: "'Chuck Lever'" <chuck.lever@oracle.com>,
"'Steve Dickson'" <SteveD@redhat.com>
Cc: "'Linux NFS Mailing List'" <linux-nfs@vger.kernel.org>
Subject: RE: Connectathon Issues
Date: Fri, 27 Mar 2015 15:00:20 -0400 [thread overview]
Message-ID: <00c601d068c0$46713c20$d353b460$@soft-forge.com> (raw)
In-Reply-To: <02E76CFB-C575-4267-83A9-448CB69AC8C6@oracle.com>
Chuck,
Here is what the systems are running,
3.10.0-123.el7.x86_64 #1 SMP Thu Sep 11 15:55:14 CDT 2014 x86_64 x86_64
x86_64 GNU/Linux
Scientific Linux release 7.0 (Nitrogen)
Thanks
Rupert
-----Original Message-----
From: Chuck Lever [mailto:chuck.lever@oracle.com]
Sent: Thursday, March 26, 2015 1:58 PM
To: Steve Dickson
Cc: Rupert Dance; Linux NFS Mailing List
Subject: Re: Connectathon Issues
On Mar 26, 2015, at 12:19 PM, Steve Dickson <SteveD@redhat.com> wrote:
>> There are several other combinations that cause other errors:
>>
>> 1. The test hangs and no error is reported. In these cases the
>> client system MUST be restarted before it becomes usable again. The
>> server system is restarted to get back to a known good state and
>> clear the exports before restarting testing
>>
>> 2. Connectathon Basic test hangs with the client system displaying:
./test5:
>> read and write
> Is it really hung or is it just slow? On the client, use tshark host
> <server> to see if there is anything going over the wire.
I'm guessing Rupert is using NFS/RDMA. If true, tshark is not going to be
helpful.
Rupert, what is the output of "uname -a" on your systems?
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
prev parent reply other threads:[~2015-03-27 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <009501d060e6$b54c3780$1fe4a680$@soft-forge.com>
2015-03-17 22:35 ` Connectathon Issues Steve Dickson
2015-03-18 1:26 ` Frank Filz
2015-03-19 15:04 ` Steve Dickson
2015-03-19 16:57 ` Rupert Dance
2015-03-26 17:19 ` Steve Dickson
2015-03-26 17:57 ` Chuck Lever
2015-03-27 19:00 ` Rupert Dance [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='00c601d068c0$46713c20$d353b460$@soft-forge.com' \
--to=rsdance@soft-forge.com \
--cc=SteveD@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/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.