Bug 123333 - NFS throughput problem
Summary: NFS throughput problem
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 2
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-17 09:43 UTC by Rene Kapeller
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-04-16 06:04:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Rene Kapeller 2004-05-17 09:43:31 UTC
Description of problem:
I have a FC2T3 nfs server and a RH-9.0 nfs client, both connected to a
gigabit switch.
Trying to write a large file (dd if=/dev/zero of=big500 bs=1M
count=500) to the nfs
server, the copy process takes minutes or infinite time. Doing the
same test, but using RH-9.0 (same hw) as the nfs server, the copy
process takes ~10 seconds.
Taking a tcpdump, I get lots of 'slsfs.nfs: 1472 write fh
Unknown/0100000200080005D5700A008A710A0084A75613D5700A0083A4A98000000000
4096 bytes @ 0x1d3d000 <unstable>'.
I also tried to increase rmem_default and rmem_max to 512k - no change.
Hardware: Dell PE2650, Broadcom Corporation|NetXtreme BCM5703X Gigabit
Ethernet
NIC driver: TG3
I was also going to test the Broadcom driver, but failed on 'bcm5700:
Unknown symbol genapic'
Kernels test so far (nfs server): 2.6.5-1.358smp and 2.6.5-1.327smp

Comment 1 Steve Dickson 2004-10-14 21:03:40 UTC
Is this still an issue with more recent FC kernels?

Comment 2 Dave Jones 2005-04-16 06:04:29 UTC
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat.  The Fedora legacy project will be producing further kernel
updates for security problems only.

If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.

Thank you.



Note You need to log in before you can comment on or make changes to this bug.