From: Stephen Hemminger <shemminger@vyatta.com>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 15517] New: big file transfers stall and break network
Date: Thu, 11 Mar 2010 08:46:30 -0800 [thread overview]
Message-ID: <20100311084630.64b85696@nehalam> (raw)
Begin forwarded message:
Date: Thu, 11 Mar 2010 14:40:12 GMT
From: bugzilla-daemon@bugzilla.kernel.org
To: shemminger@linux-foundation.org
Subject: [Bug 15517] New: big file transfers stall and break network
http://bugzilla.kernel.org/show_bug.cgi?id=15517
Summary: big file transfers stall and break network
Product: Networking
Version: 2.5
Kernel Version: 2.6.32.9
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: IPV4
AssignedTo: shemminger@linux-foundation.org
ReportedBy: conrad_s@rocketmail.com
Regression: Yes
Created an attachment (id=25475)
--> (http://bugzilla.kernel.org/attachment.cgi?id=25475)
lspci output, from working 2.6.31
Upgrading to kernel 2.6.32.9 on a 64-bit machine (Fedora 12,
2.6.32.9-67.fc12.x86_64) caused breakage in transfer of large files over SSH
and SMB, followed by breaking network access.
To reproduce, copy a large file (> 900 MB) using SSH or SMB (mounted either
directly via "mount" or indirectly via "gfvs / nautilus"). Copy stalls and
network becomes unusable (e.g. can't ssh to any other host).
Previous kernel 2.6.31.12 (Fedora 12, 2.6.31.12-174.2.22.fc12.x86_64) works
fine.
--
next reply other threads:[~2010-03-11 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 16:46 Stephen Hemminger [this message]
2010-03-11 22:31 ` Fw: [Bug 15517] New: big file transfers stall and break network Matt Carlson
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=20100311084630.64b85696@nehalam \
--to=shemminger@vyatta.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).