From: Bob Kryger <bobk@panix.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: For users of Fedora <fedora-list@redhat.com>,
nfs@lists.sourceforge.net,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: nfs write problems
Date: Wed, 03 Oct 2007 13:53:13 -0400 [thread overview]
Message-ID: <4703D709.50400@panix.com> (raw)
In-Reply-To: <20071003133118.GP21675@fieldses.org>
Sure, easily. I gziped a capture of a single test.
http://www.panix.com/~bobk/typescript.gz
the program is a simple one...
#include <stdio.h>
main()
{
unsigned long long k=0;
unsigned char byte;
while(!feof(stdin))
{
byte=getc(stdin);
if(byte!=0)
printf("nonzero (0%o) found at byte %d\n",byte,k);
k++;
}
printf("file size = %d bytes\n",k);
}
J. Bruce Fields wrote:
> On Wed, Oct 03, 2007 at 06:21:51AM -0400, Bob Kryger wrote:
>
>> Trond Myklebust wrote:
>>
>>> Feel free to describe your test in a bit more detail. Without more
>>> information, we obviously can't rule out the existence of an NFS bug,
>>>
>>>
>> I was trying to be thorough, I hope I succeeded.
>>
>
> The dd test sounded simple enough, but if you could include a transcript
> of the commands you ran (together with the C code of any test programs)
> just to be sure, that might help.
>
> --b.
>
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-10-03 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 19:56 nfs write problems Bob Kryger
2007-10-03 0:07 ` Trond Myklebust
2007-10-03 10:21 ` Bob Kryger
2007-10-03 13:31 ` J. Bruce Fields
2007-10-03 17:53 ` Bob Kryger [this message]
2007-10-04 20:12 ` [NFS] " Bob Kryger
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=4703D709.50400@panix.com \
--to=bobk@panix.com \
--cc=bfields@fieldses.org \
--cc=fedora-list@redhat.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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