AFP548 Changing the world one server at a time.

Saving files to an Isilon SMB Share from Lion

Home › Forums › OS X Server and Client Discussion › File Serving › Saving files to an Isilon SMB Share from Lion

Tagged: 

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • July 25, 2012 at 6:53 am #382610
    JonE
    Participant

    We have a number of Lion and Snow Leopard clients running Final Cut Pro 7 using an Isilon cluster as shared storage.

    When FCP7 saves it’s auto save files and User Saved project files to the Isilon, viewing them in Finder on the Lion box reports them back as a UNIX executable, and the system is unable to use them. This doesn’t happen with Snow Leopard using the same storage, where the files are identified as FCP files.

    I’ve briefly googled and found that Lion uses a new, Apple Proprietary version of SMB, so there’s a good chance that the issue is with this, although we also have some Huawei  storage, and the issue isn’t replicated here, neither (of course) to the local disks.

    I wonder if anyone else has had similar experiences? Is there a fix?

    Thanks,

    Jon

     

    July 29, 2012 at 5:43 pm #382635
    BernieC
    Participant

    Hi Jon,

    I work for EMC in the Isilon Division and have some experience with this problem.  In order to correct it, you’ll need to do a couple of things:

    1. Add .com.apple.smb.streams.on at the top-level of the SMB share, per Apple KB HT4017.  There’s probably a good chance you may have already done this, in order to force your Snow Leopard clients to use Alternate Data Streams with SMB shares.

    2. Upgrade your Isilon cluster to version 6.5.5.6 or later.  The latest general availability release is 6.5.5.7.  These versions contain fixes to the SMB server that allows us to respond to Lion clients correctly when they ask for the .com.apple.smb.streams.on file, and these versions have fixes that allow these alternate data streams to work better with Lion clients.  Snow Leopard uses a different mechanism, because it has a different underlying SMB client.  Lion, and Mountain Lion, have a newer SMB client and behave a little bit differently.

    I’m not sure what the rest of your workflow looks like, but if performance is what you’re looking for out of Isilon and all of your clients are Macs, you may want to consider using NFSv3 instead of SMB.  But, that’s a slightly different discussion 🙂

    Thanks,
    Bernie

  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.