This discussion is locked
original_macmadman

Q: File Permission problems FCP and XSAN

We have 5 Mac Pros connected to our XSAN (2 Xserves and 2 Promise arrays.). When a file is created on one of the FCP Macs and saved on the XSAN, the permission are OK (Individual - R/W, Group - R/W & Everyone RO.)

The problem is when a file, generally audio (from our sound booth or music from an outside source) or a graphic (usually Photoshop from our Graphics folks) is brought in over the LAN and save to the XSAN volume, the permissions are Individual - R/W, no group is listed and Everyone - No Access.

If they try work on something that another user started, they get permission errors if the sequence contains a file that was brought in from the outside.

I know we can change permissions on a file, but there are so many of them that it is slowing down production.

Is there anything we can do to either eliminate this happening, or have something like a drop folder they can place a file in to automatically change the file permissions?

Any help with this would be greatly appreciated.

The MacPros are running OS X 10.5.8 and FCP 7.0.3 and the XSAN is running Mac OS X Server 10.5.8 and XSAN 2.2.

Thanks.

MacPro, Mac OS X (10.5.8), XSAN

Posted on Jan 27, 2011 8:46 AM

Close

Q: File Permission problems FCP and XSAN

  • All replies
  • Helpful answers

  • by Lucas Nap,

    Lucas Nap Lucas Nap Feb 2, 2011 4:31 AM in response to original_macmadman
    Level 1 (0 points)
    Feb 2, 2011 4:31 AM in response to original_macmadman
    You should setup ACL's for this. You can set this up and propagate in the Xsan admin, the Server admin and the Terminal.
  • by jmyres,

    jmyres jmyres Feb 2, 2011 10:14 AM in response to original_macmadman
    Level 1 (80 points)
    Feb 2, 2011 10:14 AM in response to original_macmadman
    If files saved to the AFP reshare are inaccessible by the fibre clients try this in terminal on your AFP re-share...

    sudo serveradmin settings afp:lock_manager = no

    Then restart AFP (or reboot), and re-propagate permissions back to where you need them. This will hand off file locking duties from AFP to the Xsan, which will help keep your permissions correct.

    JM

    (Thanks to Shane for showing me this)