Activity › Forums › Storage & Archiving › MetaSAN with FCP on Mac OSX 10.4.8
-
MetaSAN with FCP on Mac OSX 10.4.8
Posted by Sean Oneil on October 25, 2006 at 6:06 amHas anyone experienced strage problems with rendering files? I’ve just been getting an error “File Name already exists” when I try to render. It started after updating to 10.4.8. It hasn’t been consistent and I’m not sure yet if it’s related to MetaSAN – so I haven’t emailed Bernard yet. Just wanted to know if anyone using MetaSAN has updated to 10.4.8 without problems.
Sean
Wadzunit replied 19 years, 6 months ago 5 Members · 7 Replies -
7 Replies
-
Christopher Tay
October 25, 2006 at 6:43 amHey Sean…how’s your experience with MetaSAN so far ?
In what environment are you using it (SD or HD) and how many systems are on the SAN ?
-chrispy
-
Francois Stark
October 29, 2006 at 11:55 pmNope, it’s not Metasan. I have 4 suites on os X 10.4.7 and have the same problem, using MetaSAN and SanMP. I recon it’s a FCP issue.
I even had it a few times on FCP 5.0, but it seems to have increased since I moved to FCP 5.1. Rendering just stops and it says “file name already exists”.
Regards
Francois -
Bernard Lamborelle
October 30, 2006 at 6:38 pmHi Sean,
We’ve been testing with 10.4.8 and so far we haven’t seen anything weird. This being said we haven’t completed a full QA pass on it either, and therefore haven’t added it to the list of supported builds (yet!).
Have you seen anything else strange on the SAN?
Bernard
-
Sean Oneil
November 16, 2006 at 5:28 amSorry I took so long. Don’t regularly check this board.
Yes, it had nothing to do with MetaSAN. I wasn’t sure which is why I didn’t email you Bernard.
Basically, my direct attached SATA array had become degraded (RAID 5) and this was causing the problems. After I rebuilt it and ran Disk Warrior, the problem went away.
BTW, I wanted to ask if a future version of MetaSAN will be able to ignore direct attached drives (as oppose to just mounting it as Private). This issue I had is a perfect example of how it can be problematic. I had to uninstall MetaSAN before I could successfully run Disk Warrior on it. MetaSAN also prevents me from unmounting direct attached drives. It’d be nice if MetaSAN could ignore these disks the way it ignores the system disk. Not a huge deal.
Sean
-
Sean Oneil
November 16, 2006 at 5:29 am[chrispy] “Hey Sean…how’s your experience with MetaSAN so far ?
In what environment are you using it (SD or HD) and how many systems are on the SAN ?”
It definitely does the job. I totally recommend it. There are a few minor annoyances, but overall it’s fantastic.
Sean
-
Bernard Lamborelle
November 16, 2006 at 6:48 pmHi Sean,
I know MetaSAN offers this ability on Windows, but I don’t know if it is possible on Mac. I’ll check with support and get back to you.
Thanks for the update!
Cheers,
Bernard at tiger-technology dot com
-
Wadzunit
January 23, 2007 at 2:40 amHi Bernard,
Just interested in whether or not MetaSAN under Mac OS X can ignore direct attached drives and allow them to be ejected.
thx
Adam.
Reply to this Discussion! Login or Sign Up