I'm working on the latest MC version for MAC, 6.0.1.1 using MAC OS 10.7.3 and our show is shooting on the RED Camera. The "dailies" are being processed through REDCINE-X using the RED ROCKET Card. Is anyone having issues when new Avid Media files are coppied into your Unity partition Avid Media folders and the MC rewrites the "mdb" and "pmr" files? My MC will sometimes freeze while scanning/indexing these new files. At this point both the MC and Fiber Manager software are frozen and "not responding" and need to be forced to quit. Has anyone eles had this happen and is there a solution to fixing this?

Not sure.  What version of FM are you using?  What version of Unity?  Have you checked the MC v6.0.1.1 readme to see the compatible shared storage platforms?

Unity Client Version 5.5.1

Unity Server Version 5.1.3

ATTO Celerity FC-41ES is the 4 Gb fiber channel card

ATTO Driver v 3.4.7

ATTO Firmware 2010_07_28

Mac Pro dual Quad - "Nehalem"

Core 2.66 or 2.93 GHz

OS 10.7.3

OK, here's a simple work around that I am currently using which  helps tremendously. Not only because it is working properly but also to have the piece of mind that the entire system, the Unity and the MC are in sync and stable.

Here's the idea, that a very good friend, came up with as a solution to what appears to be a software BUG in the MC 6 version for MAC.

I have two partitions on my CPU one formatted as per Avid specs to run MAC OS 10.6.8, "Snow Leopard" with Avid MC VER 5.5.3.3 and on my second partition there is MAC OSX 10.7.3, "Lion" with Avid MC VER 6.0.1.1

For my primary use and where my Main Project will run I will be using the MC 6 on MAC "Lion."

This is a bit more complicated and detailed than what i will write down here, but in a nut shell here is the process.

I will only use the MC 5 on "Snow Leopard" to drag & drop new Avid Media files, from set, onto my Unity partition being used for media storage for my show. I will run a "local" project with the identical name as per my current show. after copping my new media files I will startup MC 5 so that it scans and indexes my Avid Media folder. Once completed i need to quit out of MC 5 and reboot to my MC 6 startup partition.

At this point my normal process of ingesting new dailies into my project picks up and continues throughout the day.

Many thanks for all the assistance that many people and companies have afforded me in trying to coop and deal with this problem.

Well, if others are reporting this as an issue, we should notify Avid.  I notice you are running all of the correct versions of software, so this should be a supported situation.

Anyone else seeing this?  I need a couple more reports before I can escalate it.

may be a little late, but wanted to chime in...we have Lion machines running v5.5.3.4 and 6.0.1.1 connected to Unity 5 an had this issue as well..spoke with AVID support a while back...ended up being an incompatibility with Lion (64 bit) and Unity (32 bit)

the workaround was simply to lower file counts in the mediafiles folders...the sweet spot is somewhere around 1000 to 1500 files.  If you are creating all the files inside AVID, then the file structure that AVID creates is fine, but once you have to recreate databases, you get the locking up experience...also, make sure you trash both database files...and if you need to, create your own .2, .3, .4 folders...however many you need to be under the limit to where the database files are created correctly.

is not a problem on Snow Leopard machines, but since v6 needs Lion, upgrading the systems and keeping them on Unity MN5 introduces this issue.  very reproduceable...also, finder level copies take forever as well....long time to open folders, i have found that once they are opened and the files are scanned, copying goes much easier...so open all your folder windows first...get a cup of coffee, smoke something...whatever you want...then come back and copy things around...not too many though cause that can lock you up as well...and make you reboot and start from scratch...

Joe, thank you for posting this. I'm happy to see the follow through that explains the reason why and a proper corective approach to it. Cheers.

Thanks for the update. The file count limit makes perfect sense.

My clients have been having the same problem and I came up with the same solution. But I didn't connect the issue with the file count per subfolder. I initially was dividing the media up looking for corrupt files and not finding any. So I thought maybe it was the folder itself that was corrupt and creating new uncorrupted folders was the solution.