From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Linux NFS Mailing List <nfs@lists.sourceforge.net>,
Steve Dickson <SteveD@redhat.com>,
Chuck Lever <chucklever@gmail.com>
Subject: Re: connectathon special test failure in recent kernels
Date: Thu, 17 Aug 2006 22:55:41 -0400 [thread overview]
Message-ID: <1155869741.5594.18.camel@localhost> (raw)
In-Reply-To: <20060818025001.GI6535@fieldses.org>
On Thu, 2006-08-17 at 22:50 -0400, J. Bruce Fields wrote:
> The holey test run on its own also gives a pretty short simple test
> case.--b.
It would if it actually reproduced the problem on my setup. As it
doesn't, fsx is the second best option since it produces a full dump of
the offending file section.
Trond
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-08-18 2:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 19:20 connectathon special test failure in recent kernels Chuck Lever
2006-08-08 23:32 ` Trond Myklebust
2006-08-09 2:59 ` Chuck Lever
2006-08-17 15:10 ` Steve Dickson
2006-08-17 16:38 ` Chuck Lever
2006-08-17 17:07 ` Steve Dickson
2006-08-17 19:54 ` Trond Myklebust
2006-08-17 20:56 ` Steve Dickson
2006-08-17 22:37 ` Trond Myklebust
2006-08-18 2:50 ` J. Bruce Fields
2006-08-18 2:55 ` Trond Myklebust [this message]
2006-08-21 2:05 ` [PATCH] " Steve Dickson
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=1155869741.5594.18.camel@localhost \
--to=trond.myklebust@netapp.com \
--cc=SteveD@redhat.com \
--cc=bfields@fieldses.org \
--cc=chucklever@gmail.com \
--cc=nfs@lists.sourceforge.net \
/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