USB file copy slow

Hi. I am having some problems to copy files from USB, the process is really slow. Took 30 min to copy only 1,3 GB from the usb to my home folder. Any solution for this?
Using:
Arch Linux i686
Kernel Release: 3.0-ARCH
WM: Openbox
DE: LXDE
Processor Type: Intel(R) Celeron(R) CPU 540 @ 1.86GHz
PCManFM as fm

Arhat wrote:
Is your USB device attached via the uhci_hcd or ehci_hcd module?
(Check dmesg)
If your system is using the uhci_hcd module it will only operate at full speed 12Mbit/s (and not high speed 480Mbit/s) which means it would take at least 14 mins to copy 1,3 GB of data.
It is using uhci_hcd

Similar Messages

File copy slow, extremely slow

Hi everybody,
I'm facing a strange situation where file copy from an external drive (USB) to my hard drive (a macbook pro late 2008) is extremely slow.
I'm trying to understand what is happening and got here to get some help from experts ^^
The problem arises on some files only and is not specific to the external hard drive I use.
Once a file start to copy slowly, cancel the copy and start it again does not help. It's like the system finds it hard to copy this file.
It is generally very large file (over 5Gb).
I've used the disk utility to check the hard drive but every thing is ok.
I'm currently trying to copy a 35Gb file. The ETC is 74 hours !!!
Can somebody help?
Thanks
Pascal

Thanks Chris for your answer.
I did rest the PRAM but it does not help. I just tried to copy the same file and the ETC is 305 hours
An other idea?
Pascal

Simple Bundle file copy slow and inconsistent

We are running ZCM 11.2.3a and are experiencing slowness with some bundles.
We have a simple bundle to copy a small file to the workstation.
Sometimes the file copy is abnormally long and other times it's instant for the same bundle.
Any ideas why this would be happening.
Thanks

Try enabling Debug Logging and ZMD-Message logging to see if that helps.
Also -
Try setting up a test Location for a Device and only point that location
to Server1 for everything. Then Server 2.....
Look to see if one server is giving u issues.......
On 3/11/2014 7:46 AM, markvh wrote:
>
> The file is uploaded to the content-repo when the bundle it created.
> It has synched across all 4 servers and is available.
> I then assign the bundle to my machine and open from NAL.
> Sometimes it takes absolute ages and other times quick..
>
> Thanks
> Mark
>
>
Craig Wilson - MCNE, MCSE, CCNA
Novell Technical Support Engineer
Novell does not officially monitor these forums.
Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.

USB file copy very slow

Hi everyone, I hope that someone can help me with thisproblem:
I was copying some files of 370 MB to a 4GB Kingston USB key and It took around 45 or 50 minutes to copy it and when I try to eject the key it give me an error. I tried again and it was the same; So I remove it without unmounting...... The result, only two of all files were in the usb key.
I'm using LXDE, 2.6.30-arch on a AMD 5200 x2 64bits, 4 GB of ram.
Why it took me too long to copy those files and the error when i was rejecting the USB key???
Thanks to all, please forgive my english....

brebs wrote:
R00KIE wrote:usb flash drives have an activity led for a reason
It would not be reliable, without the flush option, to prevent excessive caching.
Yes you are right, but if lots of data is cached and you ask to unmount the drive from a DE (my experience is with xfce) then I believe there is a timeout before it spits an error about not being able to unmount while it is still trying to flush out all the data (maybe the error the OP received?), thats when the activity led is useful, to check if it is just being stubborn or actually still doing something.
I have noticed that even after xfce says it is safe to remove the device there is still activity for a couple of seconds so I guess one risks to have data loss if removing the drive while there is still activity.
The OP just said 370 MB of data and didn't mention how many files there were, from my experience you get around 5MB/s of writing speed with most usb flash drives (USB2 drives, the most common and cheaper) but this is when writing big files, try to write 300MB of small files and you will quit before it reaches 20% (if you don't count caching).
I have also noticed that even if the kernel does cache the writes it will keep writing in the background, but when unmounting there is always some writing to do so I guess either way it will not be safe to just remove the drive without unmounting first, that flush mount option may be worth looking at ...
Without more details we are all just giving our best guesses, maybe it can even be broken hardware that is causing the problem for all we know.

[Forum FAQ] Troubleshooting Network File Copy Slowness

1. Introduction
The Server Message Block (SMB) Protocol is a network file sharing protocol, and as implemented in Microsoft Windows is known as Microsoft SMB Protocol. The set of message packets that defines a particular version of the protocol is called a dialect. The Common
Internet File System (CIFS) Protocol is a dialect of SMB. Both SMB and CIFS are also available on VMS, several versions of Unix, and other operating systems.
Microsoft SMB Protocol and CIFS Protocol Overview
http://msdn.microsoft.com/en-us/library/windows/desktop/aa365233(v=vs.85).aspx
Server Message Block overview
http://technet.microsoft.com/en-us/library/hh831795.aspx
1.1
SMB Versions and Negotiated Versions
- Thanks for the
Jose Barreto's Blog
There are several different versions of SMB used by Windows operating systems:
CIFS – The ancient version of SMB that was part of Microsoft Windows NT 4.0 in 1996. SMB1 supersedes this version.
SMB 1.0 (or SMB1) – The version used in Windows 2000, Windows XP, Windows Server 2003 and Windows Server 2003 R2
SMB 2.0 (technically SMB2 version 2.002) – The version used in Windows Vista (SP1 or later) and Windows Server 2008 (or any SP)
SMB 2.1 ((technically SMB2 version 2.1) – The version used in Windows 7 (or any SP) and Windows Server 2008 R2 (or any SP)
SMB 3.0 (or SMB3) – The version used in Windows 8 and Windows Server 2012
SMB 3.02 (or SMB3) – The version used in Windows 8.1 and Windows Server 2012 R2
Windows NT is no longer supported, so CIFS is definitely out. Windows Server 2003 R2 with a current service pack is under Extended Support, so SMB1 is still around for a little while. SMB 2.x in Windows Server 2008 and Windows Server 2008
R2 are under Mainstream Support until 2015. You can find the most current information on the
support lifecycle page for Windows Server. The information is subject to the
Microsoft Policy Disclaimer and Change Notice. You can use the support pages to also find support policy information for Windows
XP, Windows Vista, Windows 7 and Windows 8.
In Windows 8.1 and Windows Server 2012 R2, we introduced the option to completely disable CIFS/SMB1 support, including the actual removal of the related binaries. While this is not the default configuration, we recommend disabling this older
version of the protocol in scenarios where it’s not useful, like Hyper-V over SMB. You can find details about this new option in item 7 of this blog post:
What’s new in SMB PowerShell in Windows Server 2012 R2.
Negotiated Versions
Here’s a table to help you understand what version you will end up using, depending on what Windows version is running as the SMB client and what version of Windows is running as the SMB server:
OS
Windows 8.1 WS 2012 R2
Windows 8 WS 2012
Windows 7 WS 2008 R2
Windows Vista WS 2008
Previous versions
Windows 8.1 WS 2012 R2
SMB 3.02
SMB 3.0
SMB 2.1
SMB 2.0
SMB 1.0
Windows 8 WS 2012
SMB 3.0
SMB 3.0
SMB 2.1
SMB 2.0
SMB 1.0
Windows 7 WS 2008 R2
SMB 2.1
SMB 2.1
SMB 2.1
SMB 2.0
SMB 1.0
Windows Vista WS 2008
SMB 2.0
SMB 2.0
SMB 2.0
SMB 2.0
SMB 1.0
Previous versions
SMB 1.0
SMB 1.0
SMB 1.0
SMB 1.0
SMB 1.0
* WS = Windows Server
1.2 Check, Enable and Disable SMB Versions in Windows operating systems
In Windows 8 or Windows Server 2012 and later, there is a new PowerShell cmdlet that can easily tell you what version of SMB the client has negotiated with the File Server. You simply access a remote file server (or create a new mapping to it) and use Get-SmbConnection.
To enable and disable SMBv1, SMBv2, and SMBv3 in Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2, Windows 8, and Windows Server 2012, please follow the steps in the article below.
Warning: We do not recommend that you disable SMBv2 or SMBv3. Disable SMBv2 or SMBv3 only as a temporary troubleshooting measure. Do not leave SMBv2 or SMBv3 disabled.
http://support.microsoft.com/kb/2696547
1.3 Features and Capabilities
- Thanks for the
Jose Barreto's Blog
Here’s a very short summary of what changed with each version of SMB:
From SMB 1.0 to SMB 2.0 - The first major redesign of SMB
Increased file sharing scalability
Improved performance
Request compounding
Asynchronous operations
Larger reads/writes
More secure and robust
Small command set
Signing now uses HMAC SHA-256 instead of MD5
SMB2 durability
From SMB 2.0 to SMB 2.1
File leasing improvements
Large MTU support
BranchCache
From SMB 2.1 to SMB 3.0
Availability
SMB Transparent Failover
SMB Witness
SMB Multichannel
Performance
SMB Scale-Out
SMB Direct (SMB 3.0 over RDMA)
SMB Multichannel
Directory Leasing
BranchCache V2
Backup
VSS for Remote File Shares
Security
SMB Encryption using AES-CCM (Optional)
Signing now uses AES-CMAC
Management
SMB PowerShell
Improved Performance Counters
Improved Eventing
From SMB 3.0 to SMB 3.02
Automatic rebalancing of Scale-Out File Server clients
Improved performance of SMB Direct (SMB over RDMA)
Support for multiple SMB instances on a Scale-Out File Server
You can get additional details on the SMB 2.0 improvements listed above at
http://blogs.technet.com/b/josebda/archive/2008/12/09/smb2-a-complete-redesign-of-the-main-remote-file-protocol-for-windows.aspx
You can get additional details on the SMB 3.0 improvements listed above at
http://blogs.technet.com/b/josebda/archive/2012/05/03/updated-links-on-windows-server-2012-file-server-and-smb-3-0.aspx
You can get additional details on the SMB 3.02 improvements in Windows Server 2012 R2 at
http://technet.microsoft.com/en-us/library/hh831474.aspx
1.4 Related Registry Keys
HKLM\SYSTEM\CurrentControlSet\Services\MrxSmb\Parameters\
DeferredOpensEnabled – Indicates whether the Redirector can defer opens for certain cases where the file does not really need to be opened, such as for certain delete requests and adjusting file attributes.
This defaults to true and is stored in the Redirector variable MRxSmbDeferredOpensEnabled.
OplocksDisabled – Whether the Redirector should not request oplocks, this defaults to false (the Redirector will request oplocks) and is stored in the variable MrxSmbOplocksDisabled.
CscEnabled – Whether Client Side Caching is enabled. This value defaults to true and stored in MRxSmbIsCscEnabled. It is used to determine whether to execute CSC operations when called. If CSC is enabled,
several other parameters controlling CSC behavior are checked, such as CscEnabledDCON, CscEnableTransitionByDefault, and CscEnableAutoDial. CSC will be discussed in depth in its own module, so will be only mentioned in this module when it is necessary to understanding
the operation of the Redirector.
DisableShadowLoopback – Whether to disable the behavior of the Redirector getting a handle to loopback opens (opens on the same machine) so that it can shortcut the network path to the resource and
just access local files locally. Shadow opens are enabled by default, and this registry value can be used to turn them off. It is stored in the global Redirector variable RxSmbDisableShadowLoopback.
IgnoreBindingOrder – Controls whether the Redirector should use the binding order specified in the registry and controlled by the Network Connections UI, or ignore this order when choosing a transport
provider to provide a connection to the server. By default the Redirector will ignore the binding order and can use any transport. The results of this setting are stored in the variable MRxSmbObeyBindingOrder.
HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\
Security Signature settings – The RequireSecuritySignature setting is stored in MRxSmbSecuritySignaturesRequired, EnableSecuritySignature in MRxSmbSecuritySignaturesEnabled, RequireExtendedSignature
in MRxSmbExtendedSignaturesRequired, and EnableExtendedSignature in MRxSmbExtendedSignaturesEnabled. Note that the Extended Security Signatures assume the regular security signatures are enabled, so those settings are adjusted if necessary based on the extended
settings. If extended signatures are required, regular signatures have to be required.
EnablePlainTextPassword – Support for using plain text passwords can be turned on using this key. They are disabled by default.
OffLineFileTimeoutIntervalInSeconds – Used to set the expiration time for timing out an Exchange (discussed later) when the exchange is accessing an offline file. This value defaults to 1000 seconds,
but can be changed in the registry and is stored in the global Redirector variable OffLineFileTimeoutInterval
SessTimeout – This is the amount of time the client waits for the server to respond to an outstanding request. The default value is 60 seconds (Windows Vista). When the client does not receive the
response to a request before the Request Expiration Timer expires, it will reset the connection because the operation is considered blocked. In Windows 8, the request expiration timer for the SMB 2 Negotiate is set to a smaller value, typically under 20 seconds,
so that if a node of a continuously available (CA) cluster server is not responding, the SMB 3.0 client can expedite failover to the other node.
ExtendedSessTimeout – Stored in the ExtendedSessTimeoutInterval variable, this value is used to extend the timeout on exchanges for servers that require an extended session timeout as listed in the
ServersWithExtendedSessTimeout key. These are third party servers that handle SMB sessions with different processes and vary dramatically on the time required to process SMB requests. The default value is 1000 seconds. If the client is running at least Windows
7 and ExtendedSessTimeout is not configured (By Default), the timeout is extended to four times the value of SessTimeout (4 * SessTimeout).
MaxNumOfExchangesForPipelineReadWrite – This value is used to determine the maximum number of write exchanges that can be pipelined to a server. The default is 8 and the value is stored in the variable
MaxNumOfExchangesForPipelineReadWrite.
Win9xSessionRestriction – This value defaults to false, but is used to impose a restriction on Windows 9x clients that they can only have one active non-NULL session with the server at a time. Also,
existing session based connections (VNETROOTS) are scavenged immediately, without a timeout to allow them to be reused.
EnableCachingOnWriteOnlyOpens – This value can cause the Redirector to attempt to open a file that is being opened for write only access in a manner that will enable the Redirector to cache the file
data. If the open fails, the request will revert back to the original requested access. The value of this parameter defaults to false and is stored in the MRxSmbEnableCachingOnWriteOnlyOpens variable.
DisableByteRangeLockingOnReadOnlyFiles – This parameter defaults to false, but if set to true will cause level II oplocks to automatically be upgraded to batch oplocks on read-only files opened for
read only access. It is stored in the variable DisableByteRangeLockingOnReadOnlyFiles.
EnableDownLevelLogOff – False by default, this value controls whether a Logoff SMB will be sent to down-level servers when a session is being closed. If this is false, and the server has not negotiated
to the NT SMB dialect or does not support NT Status codes, the logoff will not be sent because we aren’t sure that server will understand the request. The value is stored in MrxSmbEnableDownLevelLogOff.
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\
ResilientTimeout – This timer is started when the transport connection associated with a resilient handle is lost. It controls the amount of time the server keeps a resilient handle active after the
transport connection to the client is lost. The default value is 300 seconds (Windows 7, Server 2008 R2, 8, Server 2012).
DurableHandleV2TimeoutInSecond – This timer is started when the transport connection associated with a durable handle is lost. It controls the amount of time the server keeps a durable handle active
after the transport connection to the client is lost. The default value is 60 seconds (Windows 8, Windows Server 2012). The maximum value is 300 seconds.
HKLM\SYSTEM\CurrentControlSet\Services\SMBWitness\Parameters\
KeepAliveInterval – This functionality was introduced for SMB 3.0 in Windows 8 and Windows Server 2012. The witness protocol is used to explicitly notify a client of resource changes that have occurred
on a highly available cluster server. This enables faster recovery from unplanned failures, so that the client does not need to wait for TCP timeouts. The default value is 20 minutes (Windows 8, Windows Server 2012).
HKLM\System\CurrentControlSet\Services\SmbDirect\Parameters\
ConnectTimeoutInMs – Establish a connection and complete negotiation. ConnectTimeoutInMs is the deadline for the remote peer to accept the connection request and complete SMB Direct negotiation. Default
is 120 seconds (Windows 8).
AcceptTimeoutInMs – Accept negotiation: The SMB Direct Negotiate request should be received before AcceptTimeoutInMs expires. The servers starts this timer as soon as it accepted the connection. Default
is 5 seconds (Windows 8).
IdleConnectionTimeoutInMs – This timer is per-connection. It is the amount of time the connection can be idle without receiving a message from the remote peer. Before the local peer terminates the
connection, it sends a keep alive request to the remote peer and applies a keep alive timer. Default is Default: 120 seconds (Windows 8).
KeepaliveResponseTimeoutInMs – This attribute is per-connection. It defines the timeout to wait for the peer response for a keep-alive message on an idle RDMA connection. Default is 5 seconds (Windows
8).
CreditGrantTimeoutInMs – This timer is per-connection. It regulates the amount of time that the local peer waits for the remote peer to grant Send credits before disconnecting the connection.
This timer is started when the local peer runs out of Send credits. Default is 5 seconds (Windows 8).
References:
[MS-SMB]: Server Message Block (SMB) Protocol
http://msdn.microsoft.com/en-us/library/cc246231.aspx
[MS-SMB2]: Server Message Block (SMB) Protocol Versions 2 and 3
http://msdn.microsoft.com/en-us/library/cc246482.aspx
SMB 2.x and SMB 3.0 Timeouts in Windows
http://blogs.msdn.com/b/openspecification/archive/2013/03/27/smb-2-x-and-smb-3-0-timeouts-in-windows.aspx

3. How to Troubleshoot
3.1 Troubleshooting Decision Tree
1
Is the slowness occurring in browsing a network shared folder or copying a file, or both?
Browsing, go to 1.1.
Copying, go to 1.2.
Both, go to 1.3.
1.1
Is the target a DFS path or not?
Yes, go to 1.1.1.
No, go to 1.1.2.
1.1.1
Is the client visiting the nearest DFS root server and file server?
Yes, go to 1.1.1.1.
No, go to 1.1.1.2.
1.1.1.1
Browse the corresponding (Non-DFS) UNC path directly. Do you still experience the slowness?
Yes, go to 1.1.1.1.1.
No,
go to 1.1.1.1.2.
1.1.1.1.1
Issue is the particular file server responds to the share folder enumeration requests slowly. Most probably it’s
unrelated to DFS. Follow 1.1.2.
1.1.1.1.2
Issue is that client experiences delay when browsing the DFS path, but no delay is visiting the target file server
directly. Capture Network Monitor trace from the client and study if the DFS path is cracked down.
1.1.1.2
Use dfsutil.exe to clear local domain and referral cache. Then visit the DFS path again and capture Network Monitor
trace from the client to study why the client goes to a wrong file server or DFS root server.
1.1.2
Not a DFS issue. Issue is the particular file server responds to the share folder enumeration requests slowly. “Dir”
the same share folder from Command Prompt. Is it slow?
Yes, go to 1.1.2.1
No, go to 1.1.2.2
1.1.2.1
Check the number of subfolders and files in that share folder. Is the number large?
Yes, go to 1.1.2.1.1
No, go to 1.1.2.1.2
1.1.2.1.1
Try to “dir” a different share folder on the same file server, but with less items. Is it still slow or not?
Yes, go to 1.1.2.1.1.1
No, go to 1.1.2.1.1.2
1.1.2.1.1.1
Probably to be performance issue of the file server. Capture Network Monitor trace from both sides, plus Performance
Monitor on the file server.
1.1.2.1.1.2
Probably to be performance issue of the file server, particularly, of the disk. Capture Network Monitor trace from
both sides, plus Performance Monitor on the file server.
1.1.2.1.2
Same as 1.1.2.1.1.1. Probably to be performance issue of the file server. Capture Network Monitor trace from both
sides, plus Performance Monitor on the file server.
1.1.2.2
Explorer.exe browses the share folder slowly while “dir” does fast. The issue should lie in the particular SMB traffic
incurred by explorer.exe. It's a Shell issue.
1.2
Is the target a DFS path or not?
Yes, go to 1.2.1
No, go to 1.2.2
1.2.1
Is the client downloading/uploading against the nearest file server?
Yes, go to 1.2.1.1
No, go to 1.2.1.2
1.2.1.1
Try to download/upload against that file server using the Non-DFS share path. Still slow?
Yes, go to 1.2.1.1.1
No, go to 1.2.1.1.2
1.2.1.1.1
Not a DFS issue. Capture Network Monitor trace from both sides to identify the pattern of the slowness.
1.2.1.1.2
This is unlikely to occur because the conclusion is contradictory to itself. Start from the beginning to double
check.
1.2.1.2
Same situation as 1.1.1.2. Use dfsutil.exe to clear local domain and referral cache. Then visit the DFS path again
and capture Network Monitor trace from the client to study why the client goes to a wrong file server or DFS root server.
1.2.2
Same as 1.2.1.1.1. It's not a DFS issue. Capture Network Monitor trace from both sides to identify the pattern of
the slowness.
1.3
Follow 1.1 and then 1.2.
3.2 Troubleshooting Tools
Network Monitor or Message Analyzer
Download
http://www.microsoft.com/en-us/download/details.aspx?id=40308
Blog
http://blogs.technet.com/b/messageanalyzer/
Microsoft Message Analyzer Operating Guide
http://technet.microsoft.com/en-us/library/jj649776.aspx
Performance Monitor
http://technet.microsoft.com/en-us/library/cc749249.aspx
DiskMon
http://technet.microsoft.com/en-us/sysinternals/bb896646.aspx
Process Monitor
http://technet.microsoft.com/en-us/sysinternals/bb896645

USB File Transfer Slow after Update to 10.8.4

Tonight I had a strange expierence with my Macbook. I copied 6gb of video files from a USB drive while running 10.8.3. Transfer took under 5 minutes. About 30 mins later I updated the OS to version 10.8.4. Install seemed to go well and booted fine. I used the same USB drive to copy a new 6gb of video files (season 2) and the copy is taking upwards of 1.5 hours. Clearly something in the update caused the slowdown. Any ideas or similar experiences?

Choose one of the files of the type you want to open, say PDF. Then cmd-i (Get Info). In the "Open With" pane, choose the Application you want to use to open the file. Then click on change all. Do the same for TIF.

USB file copy very fast and not completed

Hello
when I try copy big files ( about 700 MB for example ) to USB device my copy speed is very fast ( about 55 MB/S ) and Copy the file is not completed. Any one can help me to solve this problem?

Linux usually doesn't copy the files all at once. You can force it to flush all
remaining data by unmounting the USB device, which will take quite a long time
if you do it immediately after issuing the copy command.
I think there is a mounting option that forces all data transfer to be done
synchronously, in case you prefer that.

N8 USB file transfers slow

It was fast at first, now we are barely pushing dialup modem speeds.
I know it's not my computer because all other USB transfers are ultra fast, it's just this phone that now transfers slow.

> Transferring smaller blocks of data is a not solution and not dealing with the problem.
It DOES work anyway. Just try, clever guy.
The problem is caused by overflowing data buffers; so sending smaller blocks is the only solution at present; if you like it or not.

Slow Files Copy File Server DFS Namespace

I have two file servers running on VM both servers are on different physical servers.
Both connect with dfs namespace.
The problem part is both servers never have same copy speed.
Sometime very slow files copy about 1MBps on FS01 and fast copy 12MBps on FS02.
Sometime fast on FS01 and slow on FS02.
Sometime both of them slow..
So as usual I reboot the servers. Doesn't work.
Then I reboot the DC01 also doesn't work. There is another brother DC02.
After I reboot DC02, one of the FS become normal and another FS still slow.
FS01 and FS02 randomly. They never get faster speed together.
Users never complain slow FS because 1MBps is acceptable for them to open word excel etc.,.
The HUGE problem is I don't have backup when the slow FS days.
The problem since two weeks I'm giving up fixing it myself and need help from you expert guys.
Thanks!
DC01, DC02, FS01, FS02 (Win 2012 and All VMs)

Hi,
Since the slow copy is also occurred when you tried the direct copy from both shared folder, you could enable the disk write cache on the destination server to check the results.
HOW TO: Manually Enable/Disable Disk Write Caching
http://support.microsoft.com/kb/259716
Windows 2008 R2 - large file copy uses all available memory and then tranfer rate decreases dramatically (20x)
http://social.technet.microsoft.com/Forums/windowsserver/en-US/3f8a80fd-914b-4fe7-8c93-b06787b03662/windows-2008-r2-large-file-copy-uses-all-available-memory-and-then-tranfer-rate-decreases?forum=winservergen
You could also refer to the FAQ article to troubleshoot the slow copy issue:
[Forum FAQ] Troubleshooting Network File Copy Slowness
http://social.technet.microsoft.com/Forums/windowsserver/en-US/7bd9978c-69b4-42bf-90cd-fc7541ccb663/forum-faq-troubleshooting-network-file-copy-slowness?forum=winserverPN
Best Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Copying speed of files has slowed down significantly

copying speed of files has slowed down significantly
and if initiate two different copy processes then it slows so much that 1 GB data takes time like it was 15GB

Again, it depends on file types. Sometimes Apple files are not single files but packages of many smaller files, for example the iPhoto Library. Right-click in Finder, if there's "Show Package Contents", then it is technically not a single file.
For simple file transfer from one machine to another per USB drive, it can save some time to zip the data before and after transfer to and from the USB drive.

File copy over AFP / SMB very slow on Mavericks

Hi guys.
I have a retina macbook pro (early 2013) and a mac mini (late 2012).
Both are running 10.9.1. The mac mini has OS X server installed and 2 USB 3.0 harddisks attached to it in RAID0.
I have a Thunderbolt display hooked up to my MBP. I have a 1gbit wired network between the two machines.
Now comes the problem: file copy from the USB 3.0 RAID array to the macbook pro over AFP or SMB is slow, I only get around 8 MB/sec.
First I thought it was a wiring issue (I created my own ethernet cables). However, I tried copying the file via SCP (i.e. SSH) and then I get 50 MB/sec. Still not close to the maximum for gigabit, but at least a lot higher than 8 MB/sec.
I tried googling if anybody else has the same issue, but couldn't really find definitive answers.
I have tried everything with both jumbo frames of and on. Both give the same results.
What's even stranger is if I connect my MBP over 5 GHz to my airport instead of wired, I get 20 MB/sec over AFP....
As far as I know the problem did not arise in the pre-Mavericks time.
Does anybody have any suggestions or solutions? 8 MB/sec is not really that nice

Have you checked your ethernet speed/duplex settings on the ethernet port and XP machine?

TC slow wired file copy

Hello,
I am trying to copy files to my TC connected with ethernet. It takes about 15 minutes to copy a 500meg file. The transfer rate will speedup and slow down dramatically during the copy. Has anyone seen this behavior? The TC is almost useless as an network storage device with this slow transfer speed. Thanks

I am having a similar problem here with the new dual-band TC on 7.4.1. My speeds are way below what I expected. I heard that the new firmware causes slowdowns, but I wasn't able to find TC 7.4 anywhere to roll back to. For me, the speeds of file copying vary between 1-4MBs on wireless and 6-8 on ethernet. And if I copy from TC to an HFS+ formatted USB Disc directly connected to it, the speeds are between 1-2 also, sometimes even slower (and I thought I'd get full USB speeds this way!). This seems terribly slow. Sometimes the HDD in TC shuts down when I am copying between it and the USB disc connected right to it (you can hear the sound of the HDD slowing down and stopping) - and I have to wake it by opening a file already on it for the copying to continue.
I will try to backup all my files on TC somewhere else and erase it from AirPort Utility, as there was an advice somewhere that formatting the disc might help. I sure hope that my device is not broken, as I'd truly hate to have to make warranty rounds...

Extremely slow file copying over airport extreme network

Hi,
I have an Airport Extreme Base Station (10/100) network, also connected to the internet. When copying files from my MacBook Pro to a USB drive connected to the base station, OR when copying files to another computer (a windows machine) the throughput maxes out at about 700 KB/sec which is 10 times slower than when copying to the USB drive connected directly to my MacBook Pro. Although I have updated everything to the latest and greatest versions, I still have very slow file copy speeds. It's always been this way. I've read dozens of threads for potential fixes but none of them have helped. I am using Activity Monitor to measure the throughput and also timing the copy of a 10GB file. At these speeds, that file takes 4 hours. Useless.
My base station is within a few feet. I've tried different channels, 2.4GHz, 5GHz, getting rid of WPA, you name it. At first I thought it might be some issue with the USB drive connected to the base station, but copying to another computer on my network is the same. It is very frustrating.
Any insights would be greatly appreciated.

Thanks. I thought about buying the TC but I'm worried that if my network is operating slowly, which it appears to be, that I'm not going to get the throughput. I also noticed that my windows machine which is on the same network accesses the internet faster as well. I'm wondering if it is something with my MacBook.
BTW - I went to school in Pittsburgh. Great great town.

MacBook slow Wifi (file copying)

Hi there,
I'm running a 802.11n 2,4GHz Wifi at home. My Mac Mini (2011) and Macbook (2007, white) connect to my network using it. My server is connected through gigabit LAN.
Using my Mini I get very decent speeds copying files, a 700MB file takes just a few seconds to copy. But using my Macbook speeds are incredibly slow.
The same file takes minutes to copy.
I've tried changing the Wifi channel and also the router without success. It seems to be a problem with my MacBook. It's running 10.6.8. Had 10.7.4 installed before, wasn't better. The Mini of course runs 10.7.4.
I also remember connecting the MacBook to a friends Wifi in 2008 who already had 802.11n and it was ultra fast. So it should be able to handle it.
Any ideas on how I can get better speeds?
Tried several channels, no interferences, signal is full bars on both machines which are sitting next to each other by the way. So no physical objects blocking the MBs wifi. Also did a clean install on 10.6.8.
Help!?

Thank you for your reply.
I think we have the very same Macbook.
As yours mine is maxed out with 4GB of installed RAM, where 3GB can be addressed. Same specs as you see.
Also I'm not running anything except Finder when testing. Currently there's plenty of RAM free. With Safari, Mail and iTunes open I still have 800MB free.
I'm going to install Leopard or even Tiger on a spare partition, just for testing..
By the way, did you try Lion? Even in 10.7.4 I had Wifi drops on wakeup plus the same slow file copying speeds..

Slow file copy speeds

Hello, I can't ul or dl files from client to me or vice-versa faster than 70kbs. Both connections are static, both are 7mbs up and 2.5+mbs down and both isps have assured me that no throttling is taking place. Ports are set correctly, encryption is off for file copy; I am only one guy managing one machine for my dear gray haired mother. The files are huge 300megs plus (.psds with necessary layers, etc.) but it doesn't seem to make any diff. if I copy 1 at a time or zip a bunch-- no faster than 70k and usually 50k. Routers on both ends say connected at 7up/2.5 down and any ftp client flies to and fro. It is just much more convenient to use ARD 3.2--
Gracias, Dennis

Welcome to the Discussions Dennis,
Are you using the Copy command while also Viewing or Controlling?
Things that I can think off of the top of my head that could be slowing things down (on one of the machines):
bandwith use from screen sharing
A FAT formatted drive
encrypted user or folder
difference in OS (10.5 to 10.4 - sad but true at times)
encrypted transfer (which you covered)
3rd party firewall / security sw
I've also seen where you may be able to do a good speed test, but due to router port forwarding using ARD to transfer files is slow, so that would be one other thing to check.
Sorry I don't have a know cause. I hope this helps, JD

USB file copy slow

Similar Messages

Maybe you are looking for