[ENBD] 2.4.30 problems with big file transfers (1 GB)

ckoepp enbd@lists.community.tummy.com
Thu, 20 Feb 2003 07:39:14 +0100


This is a multi-part message in MIME format.

------=_NextPart_000_0045_01C2D8B3.2A6876B0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,

during the last days I played around with the ENBD Version 2.4.30 and =
observed a problem with copying bigger files.

Client:=20
Is a Pentium 3  700MHz with Intel Ethernet Pro 100 NIC.
Debian Woody and at first a self compiled Kernel 2.4.18 and later =
(during my tests) I changed to 2.4.20.

Server1:=20
Celeron 366 MHz with the same NIC.
Suse 7.3 Distribution

Server2:=20
Pentium 1  133 MHz with the same NIC.
Debian Woody and a self compiled Kernel 2.4.20.

Reading a 1 GByte File from the server1 works fine: Transfer Rate about =
5.5 MB/s. The HUB utilization scale goes up to 80 percent.
Writing  the same file back to the server: Transfer Rate about 500 kB/s. =
The HUB utilization scale goes only up to 10 percent - usually it's =
lower.

During my test I switched from Kernel 2.4.18 to 2.4.20, I changed the =
HUB and I tried Server 2. Always the same result.

The last thing I did -  I tried NBD Version 2.4.29 and everything works =
fine, reading and writing works nearly with the same speed.=20
So I think there is a problem on Version 2.4.30 - any ideas?

Thanks!

Carsten

------=_NextPart_000_0045_01C2D8B3.2A6876B0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3314.2100" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>during the last days I played around =
with the ENBD=20
Version 2.4.30 and observed a problem with copying bigger =
files.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Client:&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Is a Pentium 3&nbsp; 700MHz with Intel =
Ethernet Pro=20
100 NIC.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Debian Woody and at first a self =
compiled Kernel=20
2.4.18 and later&nbsp;(during my tests) I&nbsp;changed to =
2.4.20.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Server1: </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Celeron 366 MHz with the same =
NIC.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Suse 7.3 Distribution</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>Server2: </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Pentium 1&nbsp; 133&nbsp;MHz with the =
same=20
NIC.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Debian Woody and&nbsp;a self compiled =
Kernel=20
2.4.20.</FONT></DIV></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Reading&nbsp;a 1 GByte File from the =
server1 works=20
fine: Transfer Rate about 5.5 MB/s. The HUB utilization scale goes up to =
80=20
percent.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Writing&nbsp; the same file back to the =
server:=20
Transfer Rate about 500 kB/s. The HUB utilization scale goes only up =
to&nbsp;10=20
percent -&nbsp;usually it's lower.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>During my test I&nbsp;switched from =
Kernel 2.4.18=20
to 2.4.20, I changed the HUB and I tried Server 2. Always the same=20
result.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The last thing I did -&nbsp; I tried =
NBD Version=20
2.4.29 and everything works fine, reading and writing works nearly with =
the same=20
speed. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>So I think there is a problem on =
Version 2.4.30 -=20
any ideas?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks!</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Carsten</FONT></DIV></BODY></HTML>

------=_NextPart_000_0045_01C2D8B3.2A6876B0--