-
Filesystem busy / binSave errors occuring randomly in MC 6.0.1
Hi,
We’ve seen the following error occurring on a semi regular basis.
Randomly while an editor is working and they go to save their bin (or it autosaves) they get a message that says “Filesystem busy, retrying (deleting old bin file)” Screenshot: https://i.imgur.com/XQFwT.png
When that fails or we command+. out of it it raises a message “binSave: error deleting old bin file” Screenshot: https://i.imgur.com/MZife.png
If we hit Try some more it gets stuck in a loop of these steps. If we hit Raise Error it shoots up an message saying “Exception: Resource busy, filename:” followed by the path of the bin.
The same messages come up when trying to close the bin as it was never able to successfully save.
What we’ve been doing to get around this is once the message comes up we create a new bin and duplicate everything over to it (which is able to save). Then in finder delete the .lck file for the bin. At this point when you go back into Media Composer and try to close the bin you get the options “save as” or “don’t save”. We click don’t save, delete the trouble bin, and continue working with the new one.
Does anyone know what might be causing this or if there is anyway to prevent it from happening?
We’re running Media Composer 6.0.1 on OS X 10.7.2 and ISIS Client Manager 3.5.0. We’ve seen the error occur on two separate shows (which are working on two separate Isis), on multiple differently configured iMacs and Mac Pros, and for multiple different users.
Thanks!
-
2 Replies
-
I am seeing this same error message with the same configuration. I have systems running 5.5.3 on the same Isis, which have never reported this error. Seems to be specific to MC 6.0.1 on OS 10.7.2 with Isis 5000. I just spoke with Avid about this problem and will relay any information they have. Let me know if you have found any solutions on your end.
Thanks
-
I’ve got the same issue except it’s even worse, bin may disappear altogether… (Avid 5.5.3.3 on OSX 10.6.8)
I’ve made a very detailed post on Avid’s forum: https://community.avid.com/forums/t/109169.aspxAvid says they’ve seen this problem on a few OSX systems around the world but they are still unable to track down the issue…
Have you found a solution or a workaround?
Reply to this Discussion! Login or Sign Up