public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Houston, we have a problem: big file copying, USB, external disks
Date: Mon, 18 May 2009 14:08:14 +0200	[thread overview]
Message-ID: <20090518120814.GK28462@charite.de> (raw)
In-Reply-To: <865071.76281.qm@web26106.mail.ukl.yahoo.com>

* John Zupfel <jzupfel@yahoo.co.uk>:
> 
> Are recent kernels (since somewhere around 2.6.27 - 2.6.28)
> choking on big file copying?
> 
> 
> https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/197762?comments=all

Does this happen AFTER a suspend/hibernate or ALL THE TIME?

> > No, it's not Ubuntu specific and Canonical didn't cause it.
> > 
> > Right now I'm copying between two SATA drives, connected to my PC via
> > eSATA.  So far a lousy 600MB has been copied and I'm already down to
> > 5MB/s and falling.
> > 
> > Here is what I know about the problem:
> > 
> > It affects ALL hardware.
> > 
> > It affects ALL file copying connections to varying degrees: USB,
> > network, SATA/eSATA.
> > 
> > In some instances, it also affects multitasking, all but locking the
> > computer up despite little to no CPU use in System Monitor.
> > 
> > There are no error logs, messages or anything else that occur when the
> > problem is happening.
> > 
> > In my experience, if you test for the problem and nothing seems to be
> > wrong, then that's because you aren't copying enough data, you don't
> > know how fast your hardware should be copying files, or you are lucky
> > enough to only be subtly affected that time.  Try copying more multi-
> > gigabytes of data, several times and see if you can't get wildly
> > different durations for the same data size.  As I state above, all
> > hardware I have tested is affected to varying degrees, some hardware
> > shows minor performance degradation over time, some hardware is all but
> > useless for file copying.
> > 
> > If you ask me, it's either the scheduler (GUI lockups with no CPU usage
> > makes me think this) or whatever performs the actual file copy process.
> > It's definitely not a USB problem because it affects network copying
> > too.
> 
> 
> 
>       
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netzwerk
  Charité - Universitätsmedizin Berlin
  Campus Benjamin Franklin
  Hindenburgdamm 30 | D-12200 Berlin
  Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
  Ralf.Hildebrandt@charite.de | http://www.charite.de

  reply	other threads:[~2009-05-18 12:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 11:57 Houston, we have a problem: big file copying, USB, external disks John Zupfel
2009-05-18 12:08 ` Ralf Hildebrandt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-18 13:47 John Zupfel
2009-05-18 16:14 ` Simon Holm Thøgersen

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=20090518120814.GK28462@charite.de \
    --to=ralf.hildebrandt@charite.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox