Skip navigation

Finder kills my NAS connection...

2491 Views 10 Replies Latest reply: May 2, 2013 3:27 PM by Banananassss RSS
bonfire Calculating status...
Currently Being Moderated
Sep 4, 2012 1:38 PM

Hi there, I've struggled for years dealing with a mysterious NAS problem (a dns-323, two of them actually).  It seems to work at first, then it slows to a crawl.  I think I've finally clued in that its Finder that is screwing things up.   Finder seems to work at first, my NAS shows up in Finder, I can click to connect, browse files, etc, all looks good.  And if I start a fresh connection and immediately transfer one big file, I get about 15-20 MB/sec data transfer rates, just as it should be.  However, if I start browsing around the NAS using Finder, the connection immediately slows to a crawl.  So I started avoiding Finder and using Terminal commmands for everything, I mount like this:

 

mkdir /Volumes/nas1

mount -v -w -t smbfs //user:password@nas1/nas1 /Volumes/nas1

 

That works fine.  I then can use any one of several protocols to transfer files to/from the nas, including cp, rsync, etc...  As files transfer, I can use a separate terminal window to monitor the progress of the transfer.  For example, if I'm copying a directory from my NAS back to my local disk, I do something like "du -sh /Users/rob/new-directory" to watch the directory grow in size, and sure enough its giving me anywere from 10-20MB/sec depending on if their small files or one big file, as to be expected...  All good, right?

 

HOWEVER, as soon as I open a Finder window (while the copy processs is still running from the terminal window) and then navigate to my NAS, the copy process immediately slows down to a crawl, like, 1MB per minute.  And it never recovers.... All subsequent interaction with the NAS is hopelessly slow.  The only way to fix it is to kill the copy job, unmount/eject the NAS and start a new NAS connection.  I've repeated this several times and get the same results always...

 

BTW - I believe I can even connect with Finder (rather tham mounting manually from a terminal command line).  But as soon as Finder tries to browse any files or directories on the NAS, thats when it chokes...  I just avoid Finder completely because I don't want to accidentally kill a big copy/rsync job in progress...

 

Sooo... what the heck is going on, why does Finder freeze up my connection???  Is there anything I can do?  It would sure be nice if Finder worked as well as terminal commands.   Any help, hints or thoughts would be much appreciated!

 

BTW - I'm running a MacPro (early 2009) w/ OS X 10.6.8

 

Thanks,

Rob

Mac Pro, Mac OS X (10.6.8)
  • akouris Calculating status...
    Currently Being Moderated
    Sep 12, 2012 2:15 PM (in response to bonfire)

    Did you manage to find a solution? Because I have a similar problem, and it is frustrating.

     

    I have a Drobo FS NAS, connected to my 2008 imac with ethernet 1gbit, and I have a similar, erratic behaviour.

  • akouris Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 13, 2012 12:06 AM (in response to bonfire)

    I have also updated, but with no improvement.

     

    I get consistent speeds with other copy methods, command line, or the muCommander which has internally a similar approach http://www.mucommander.com

     

    Whenever Finder performs a task, everything will slow down.

     

    I am thinking of temporarily setting up a windows server, share the NAS volume through that, and see if I have a more consistent connection that way.

  • akouris Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 14, 2012 4:31 AM (in response to bonfire)

    I don't use the NAS for time machine or home directory backups - I use it as a storage medium for my projects.

     

    Regardless, I often use Disk Utility to repair permissions - usually once a week, so locally my permissions are correct.

     

    You are right - permission rights can create a lot of problems, and as I understand permission issues are even greater with Mountain Lion, because in many occassions Mountain Lion "sandboxing" will not allow apps to use network storage to store critical data.

     

    Setting permissions on a shared/NAS resource is another issue.

     

    Whenever I've tried to do that I've been unable, although I do not believe that the incosistent Finder behaviour on my NAS is related to that.

  • akouris Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 22, 2012 11:40 PM (in response to bonfire)

    Something really strange is going on.

     

    There is severe incosistency in the way OSX communicates with the NAS.

     

    I do not know whether this is OSX's or the NAS's fault.

     

    The biggest problem that I experience is "browsing" through the NAS folders: I might get instant response for the directory listing, or I might wait for 90 seconds for the list of files to appear.

     

    On file transfers, I might be able to read something at 60MB/sec, and that might drop to 8-9MB and then return to 55MB. On write I might write at 25MB, fall to 12MB, then go back to 20MB.

     

    I tried something else, and I had some interesting results: try accessing the NAS from a virtual windows machine on your OSX. I did that with a Windows XP installation. The results where very revealling. Browsing through the NAS is extremely fast - I get directory listings as if the disc is local. I also get image thumbnails etc. instantly - the NAS does have a consistent response. Transferring files is slower than the peaks the OSX demonstrates (up to 50% less on copy from NAS, 20% less on write to NAS), however the virtual windows machine has consistency - the speed remains always the same.

     

    Since I see speed/response incosistency to the way NAS and OSX connect, even though I have tried both AFP and SMB, someking of other incompatibility exists between the NAS and the OSX.

     

    I am thinking of a way to re-share a mapped NAS drive from a windows virtual or physical machine, access it through the OSX and see whether a consistency in access exists.

     

    Message was edited by: akouris

  • rg_dude Calculating status...
    Currently Being Moderated
    Feb 21, 2013 11:18 AM (in response to bonfire)

    Have you tried disabling Named Streams on your Mac(s)? See: http://support.apple.com/kb/HT4017

  • Banananassss Calculating status...
    Currently Being Moderated
    May 2, 2013 3:27 PM (in response to rg_dude)

    Thanks dude, that seems to have mostly fixed things for me. I can now eject, or at least force-eject the volume which was imposibble before without restarting the Finder. Also, I notice it has killed constant network access (about 1Mb/sec reading) to Volume_2 when mounted.

     

    Non-raided DNS 323 with default mounts (Volume_1, Volume_2) on OS X 10.7.5.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.