Finder displays NFS mount only few directorys deep

Discussion in 'Mac OS X Server, Xserve, and Networking' started by Yhanthlei, Aug 17, 2012.

  1. macrumors newbie

    Aug 17, 2012
    Hey Everybody!

    I recently had the idea to hook up a large drive to my Raspberry Pi
    (if theres anybody who doesn't know those: Tiny ARM computer,
    about 30$, go buy one now!) and set up an NFS share.

    Everything working fine so far, read/write access from both a 10.6.8
    and a 10.8.0 machine.

    BUT: Navigating through the share in Finder only works a few levels
    deep, then trying to open another directory it just displays it as empty.
    No problem visiting it from the terminal, opening files from there
    works flawless as well (pictures, music, videos).

    Trying to copy something by dropping it on the (seemingly empty)
    directory in finder really upset it: It kept trying to start copying,
    actually created the subfolder, but that's it. Ended up having to
    force quit finder...

    At first I assumed it to be a bug in 10.8.0, but my snow leopard machine
    shows the exact same behaviour!

    Anybody experienced something similar before? Or has any idea

  2. macrumors 65816


    May 20, 2002
    Dallas, TX USA
    Is it a directory depth issue or is it a path length issue?

    Try creating one-character directory names and see if you can drill down in Finder.

  3. thread starter macrumors newbie

    Aug 17, 2012
    Thanks a lot, unfortunately there doesn't seem to be any connection
    to path length, but neither to directory depth! I created a few nested
    directories with a file each, but finder can't even display the first...
    I can also dig about three directories deep into my music, but can't
    even see the content of the folder "movies" that's located right above
    root... I guess something's pretty wrong here, but I'm completely
    out of ideas!
  4. macrumors 65816


    May 20, 2002
    Dallas, TX USA
  5. thread starter macrumors newbie

    Aug 17, 2012
    Thanks again,

    actually a little less then 256MB, it's shared with the GPU.
    That was my first thought as well, and memory usage is pretty high,
    but not especially high trying to access via the finder, and I'm not
    sure what difference that could make. I assume opening a directory
    in finder _shouldn't_ be more taxing for the server than an 'ls' in
    terminal... Streaming high bitrate media from the device hasn't been
    a problem either, and I guess that should put a lot more strain on
    the server than, say, listing a directory -.-

    Do you have any idea what finder could actually be doing? Maybe doing
    some sort of indexing the share doesn't like?

Share This Page