You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Strange problem when copying files to NAS

Hello all. I have a strange problem when trying to copy files from my intel iMac to my Seagate NAS. I am copying files from my HD and when the file is nearly copyied i get an error message saying that the file can't be copied because it is already in use by another application. Well... it surely isn't. I try copying them by ftp (Filezilla) and everything works fine. I can then access them through my media server but !!!! NOT THROUGH MY iMac!!!! It is like the files are not there!!!! But they definetely are! I tried fixing the disk permissions, rebooting NAS, iMac etc but nothing seems to solve the problem. Is there any suggestion of what might be wrong? I am under Mavericks and i am pretty sure that the problem started after the update. When copying from my external USB hard drive to my iMac HD everything works fine. The problem is from my iMac to my NAS.

iMac, OS X Mavericks (10.9)

Posted on Nov 1, 2013 1:34 AM

Reply
109 replies

Jan 3, 2015 9:33 AM in response to arabesc

Interestingly, most of the suggestions here does not matter IF you restart your OSX. Restarting grants some time before the bug hits again.

It doesn't matter that much is it list view or something else, its purely in the stack of OSX that is buggy.


Restarting does help however.


My NAS is "homemade" and therefore no additional software is installed, yet I see the problem on Mavericks. It is however random, since I do not get that on every restart.

Feb 9, 2015 3:10 AM in response to imbrandon

Disabling "Show icon preview" in finder resolved this issue for me too.


Any movie file formats that Yosemite can play (avi, mp4) won't copy via Finder to my Buffalo Linkstation but files that it doesn't recognise like mkv files (Finder calls these Unix Executable Files) copy fine. I think that Finder must be reading part of the file in order to get the image for the icon preview and this is causing Finder to report it is is use when copying to a nas.

Feb 9, 2015 3:32 AM in response to tatty27

Forget what I just said, it copied one avi and then a mkv without issue but it got to the next avi and fell over just as it got to the end of copying it.


It's funny but when I bought this imac everyone said that once you buy mac you never go back so why do I find myself having to use Windows via parallels to perform even the simplest of tasks?

Feb 17, 2015 6:33 AM in response to deltamc15

I have the same issue copying to my buffalo linkstation 1TB drives. I am using a brand new imac w the 4k screen running latest version of Yosemite etc. Among other things, I can't move gopro videos from the camera to the NAS even if i try to move files to imac first. I even asked at the store before i purchased the imac if the imac is compatible with the few items of other hardware i have (i.e. the buffalo NAS) and the guy said "why wouldn't it be." Wrong. My home network, with networked smart TVs, mirrored NAS drives, laptop, separate WAP, gigabit POE switch and router etc., has worked GREAT for YEARS with my 10 year old dell PC. The PC is still running and it is a good thing because i need it to do the stuff the imac cant. Tricky stuff like copying a file from one device to another.


I spoke to apple tech support yesterday and they said i will need to give them more info about what software my linkstation is running etc, and I will do that for them as soon as I get the time, but then i discovered this thread (yes, i should have searched the internet for the issue a bit harder before calling tech support). Seems like it is a well known issue and they should have all the info they need because it is not just my NAS but most NAS drives that the imac is having trouble with.


Apple - please fix this bug asap. Thanks.

Feb 19, 2015 7:06 AM in response to Jason Harder

Adding some info here:


Qnap is a TS-419 Pro II (Firmware 4.1.2) with a Raid-5 volume. NAS can be accessed locally via a gigabit connect to an AVM Fritz!Box 7390. WiFi is on.


Accessing the Qnap from my MacBookPro11,3 running OSX.10.2 via Bonjour, AFP or SMB leads to the same behaviour:


First (of multiple, if so) large files on a copy fails at the very end of file 1. The Finder cancels the other files copy.


It does not make a difference if the MBP is connected via Ethernet or Wifi.

Feb 20, 2015 6:48 AM in response to Jason Harder

Hi all,


I was having the same problem with a Linux (CentOS) server. I installed a vanilla CentOS 6 server, attached a bunch of storage to it, installed samba, and created some shares. Windows machines could connect and work just fine off of it. Macs couldn't. The finder would drop files, the finder would error out with the "file is in use" error, all sorts of horrible things going on. Tried modifying all the parameters for locking in the smb.conf file, tried playing around with sockets, turning off .DS_Store creation, turing off finder icons/previews, installing Thursby Dave to get around Apple's SMB implementation... still no joy. Finally.... I figured it out.


I went to Samba's site, downloaded, compiled and installed Samba 4.1.16.


Now, connecting via smb:// is working perfectly. No errors about files in use, speed is pretty good, and everything just seems to be working out fine.


Many of the older NAS boxes probably are using an older, more stable kernel version that has an older samba server (my version prior to the new install was 3.6.23, which is the latest you can get from the CentOS yum repositories). So unless you can update your server software, you're probably hosed.


Best of luck to you all!

Paul

Feb 26, 2015 4:11 AM in response to deltamc15

I experience the same problem "file in use" error when trying to copy or move esp. larger files from the mac to the NAS. Have to use FTP or a finder replacement (muCommander) to make it work, but then the speeds are terrible.


Using QNAP TS119 very latest firmware and Yosemite 10.10.2.

This problem has been around since Mavericks! And still not solved. QNAP forum is full of messages with same problem. I am amazed that Apple still has no solution.

Feb 26, 2015 9:53 AM in response to MickNL

I've entered a bug report with apple and they have asked for some diagnostic information (including packet captures) which I have sent to them. Hopefully will get a resolution.

One thing I noticed is that more often than not I can copy a folder of files without problems, but encounter problems when selecting and copying multiple files as a group.

While this problem gets sorted out I've switched over to using AFP with my QNAP.

Feb 28, 2015 11:50 AM in response to bti_jet

I think I've (re)discovered the fix for this.


If you've access to the Samba server, add the following to the [global] section of 'smb.conf'...


veto files = /._*/.DS_Store/.Trashes/.TemporaryItems/

delete veto files = yes


If you haven't, execute the following from a terminal shell...


defaults write com.apple.desktopservices DSDontWriteNetworkStores true


The last two items in the veto files list aren't essential, but won't cause any harm.


You'll need to restart samba (in the first instance) or logout and in again (in the latter) for the changes to take effect.


I personally haven't tried the latter variant, but have seen it quoted elsewhere.


I hope this helps,

-- Adrian

Mar 6, 2015 6:49 AM in response to Adrian Day

Adrian,


Your veto files works for the most part, but you have to change it to this:


veto files = /.DS_Store/.Trashes/.TemporaryItems/

I've found that some applications (MS Excel, Photoshop, Maya), when saving, create a ._ file. If you veto those, you can't save any documents from these applications, and possibly others.

Best,

Paul

Strange problem when copying files to NAS

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.