From: Steve Dickson <SteveD@redhat.com>
To: Rupert Dance <rsdance@soft-forge.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Connectathon Issues
Date: Thu, 26 Mar 2015 13:19:43 -0400 [thread overview]
Message-ID: <55143FAF.7090200@RedHat.com> (raw)
In-Reply-To: <003701d06265$b85ce8e0$2916baa0$@soft-forge.com>
Sorry for the delayed response
On 03/19/2015 12:57 PM, Rupert Dance wrote:
> We tried uncommenting the code but we are still seeing failures. We are
> running Connectathon on a variety of systems pairs testing both Mellanox and
> Intel Hardware. Most of the combinations pass the Connectathon Basic,
> Locking and Special tests but fail the General tests with the error message
> "Nroff ./stat: no data in nroff.time"
What does output from the time command look like?
>
> 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...
steved.
next prev parent reply other threads:[~2015-03-26 17:19 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 [this message]
2015-03-26 17:57 ` Chuck Lever
2015-03-27 19:00 ` Rupert Dance
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=55143FAF.7090200@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rsdance@soft-forge.com \
/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.