From: Bill Davidsen <davidsen@tmr.com>
To: Florin Iucha <florin@iucha.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.21-rc1: CIFS cheers, NFS4 jeers
Date: Wed, 28 Feb 2007 08:35:54 -0500 [thread overview]
Message-ID: <45E5853A.3060901@tmr.com> (raw)
In-Reply-To: <20070228040345.GL29073@iucha.net>
Florin Iucha wrote:
> On Tue, Feb 27, 2007 at 09:36:23PM -0500, Bill Davidsen wrote:
>
>> Florin Iucha wrote:
>>
>>> Hello, it's me and my 70 GB of photos again.
>>>
>>> I have tested both CIFS and NFSv4 clients in kernel 2.6.20-rc1 . CIFS
>>> passed with flying colors and NFSv4 stalled after 7 GB.
>>>
>
>
>> Neil has been diddling NFS, I did some light testing with 2.6.20-git14
>> with 190GB of mp3 and mpg files (library of congress folk music) without
>> hangs. Just "did it work" tests, copy 20-30GB to server, do md5 on the
>> data pulled back from the server.
>>
>> Didn't hang, performance testing later.
>>
>
> 2.6.20-rcX used to copy all files then hang on certain operations that
> I think used the VFS. 2.6.21-rc1 stalls the NFS transfer itself after
> several GB. The data was never corrupted.
>
> Have you tried copying _ALL_ 190 GB to the server?
No, but as noted I was doing 20-30GB, so if "several" is a small number
I'm not seeing that behavior. I'm using a Gbit connection if that is not
the same as your setup. I have additional testing queued for time
available this week.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2007-02-28 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 6:45 2.6.20-rc1: CIFS cheers, NFS4 jeers Florin Iucha
2007-02-26 6:48 ` Correction 2.6.21-rc1 Was: " Florin Iucha
2007-02-28 2:36 ` Bill Davidsen
2007-02-28 4:03 ` 2.6.21-rc1: " Florin Iucha
2007-02-28 13:35 ` Bill Davidsen [this message]
2007-03-01 5:52 ` 2.6.20-rc1: " Andrew Morton
2007-03-02 3:02 ` Florin Iucha
2007-03-02 14:39 ` Florin Iucha
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=45E5853A.3060901@tmr.com \
--to=davidsen@tmr.com \
--cc=florin@iucha.net \
--cc=linux-kernel@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.