Matthew Christy
Level 1
(35 points)
Q: Problems saving files on XSan and Final Cut Pro 6.0.2
Hello All,
We're running into very frustrating issues as we are trying to save and open Final Cut Pro project files. We are currently using an XSan with ACLs set up to store FCP documents and related files. The six workstations aren't directly attached to the SAN, they connect via GigE to AFP shares (not an ideal solution, but it's what we can afford right now). It should be noted that our setup is currently using the "Golden Triangle" of directory services (AD user accounts and groups).
In December we upgraded our XSan to version 2 (which was a nightmare in itself), and all of our clients were upgraded to 10.5 with FCS2. After the upgrades, a few issues have arisen:
1. When a user attempts to save a FCP project, sometimes they receive the error message that the file is locked. From what I read on apples support site, this is due to permissions-- a file cannot be saved by one person, and then opened and saved by another. If the ACLs set on the folder reflect the groups that have full access to the files in which the project resides (recursively), why is this an issue? Or is this just another case of bad execution on apples part?
2. After concluding a "Save As", most of the time the alternate project file is able to be opened. We've run into several instances, however, when the project file is a very small size (16k or so), and gives the error message "Unable to open project file".. and it's pretty much trash. In these cases, the autosaves are behaving in a similar manner, being a very low size and not opening.
So my question is, does this all sound like permissions issues.. or is there something inherently wrong with the XSan at this point (e.g. corruption)? How are other people using XSan volumes in conjunction with FCP 6.0.2/FCS2 to edit and store files? Perhaps we're going about the whole setup the wrong way..
Thanks for your time and any advice you can provide..
We're running into very frustrating issues as we are trying to save and open Final Cut Pro project files. We are currently using an XSan with ACLs set up to store FCP documents and related files. The six workstations aren't directly attached to the SAN, they connect via GigE to AFP shares (not an ideal solution, but it's what we can afford right now). It should be noted that our setup is currently using the "Golden Triangle" of directory services (AD user accounts and groups).
In December we upgraded our XSan to version 2 (which was a nightmare in itself), and all of our clients were upgraded to 10.5 with FCS2. After the upgrades, a few issues have arisen:
1. When a user attempts to save a FCP project, sometimes they receive the error message that the file is locked. From what I read on apples support site, this is due to permissions-- a file cannot be saved by one person, and then opened and saved by another. If the ACLs set on the folder reflect the groups that have full access to the files in which the project resides (recursively), why is this an issue? Or is this just another case of bad execution on apples part?
2. After concluding a "Save As", most of the time the alternate project file is able to be opened. We've run into several instances, however, when the project file is a very small size (16k or so), and gives the error message "Unable to open project file".. and it's pretty much trash. In these cases, the autosaves are behaving in a similar manner, being a very low size and not opening.
So my question is, does this all sound like permissions issues.. or is there something inherently wrong with the XSan at this point (e.g. corruption)? How are other people using XSan volumes in conjunction with FCP 6.0.2/FCS2 to edit and store files? Perhaps we're going about the whole setup the wrong way..
Thanks for your time and any advice you can provide..
Mac OS X (10.5.6)
by Eric A. Peters,Solvedanswer
Eric A. Peters
Level 1
(25 points)
Matthew,
If I'm reading your post correctly, it sounds like your issues are stemming from opening FCP project files directly off the XSan. Is this true? FCP will not reliably "play nice" with XSan in this way... You should "work locally, save globally" with regard to FCP projects. Any project you want to open and work in, you should pull off of the XSan to your local storage on your Mac and save that altered project back to the XSan when you are done with it. This will eliminate the permission issues you seem to be having. Even doing the "Save as" trick is a risk. I've seen plenty of FCP projects on the XSan become corrupt due to this issue, not to mention that if your XSan volume would crash and all data lost (trust me, it can happen... we've dealt with a couple catastrophic crashes), you would hate to have the only copy of your project saved on the XSan.
If I'm reading your post correctly, it sounds like your issues are stemming from opening FCP project files directly off the XSan. Is this true? FCP will not reliably "play nice" with XSan in this way... You should "work locally, save globally" with regard to FCP projects. Any project you want to open and work in, you should pull off of the XSan to your local storage on your Mac and save that altered project back to the XSan when you are done with it. This will eliminate the permission issues you seem to be having. Even doing the "Save as" trick is a risk. I've seen plenty of FCP projects on the XSan become corrupt due to this issue, not to mention that if your XSan volume would crash and all data lost (trust me, it can happen... we've dealt with a couple catastrophic crashes), you would hate to have the only copy of your project saved on the XSan.
