This discussion is archived
773 Views 3 Replies Latest reply: Sep 7, 2005 4:05 PM by Greg Plassmeyer1
Currently Being ModeratedAug 23, 2005 10:31 AM (in response to Billy Yu)I have seen something similar prior to Xsan. It was on a Cinewave card, it would create a file as big as the drives was, if you were capturing NOW, but if you set an In and Out point then it worked. It was a driver problem.
What card are you using to capture? Does it do the same thing on the internal drive? You can capture 10 Bit to the internal drive, it works fine if you are just running a test capture.
Currently Being ModeratedAug 23, 2005 11:12 AM (in response to Kalagan)We are using KONA 2 cards here. I'm continuing to run test with the internal but we cannot reproduce the same problem.
Currently Being ModeratedSep 7, 2005 4:05 PM (in response to Billy Yu)Hi there Billy. I had the same problem. And I to am using the Kona cards and versions of the OS and FCP. It does seem to be some bug in FCP that is causing this problem. The way we get around is to first avoid using the "capture now" command. But when we have to we just monitor the available space and if it all of a sudden disappears then we can go back and delete that FCP file from the XSAN. It is usually only a 8k file in the finder. But when you delete it you will get all your space back.
The command line version is to
ran this command:
server name:/volumes/xsan admin$ du -hc
found this file: 912G ./FCP /Capture Scratch/Untitled Project 1 (showed as 8k in finder)
ran this command to remove it: server name:/volumes/xsan/FCP /Capture Scratch admin$ sudo rm -R Untitled\ Project\ 1/
in this case the file was named Untitled Project 1.
Hope this helps you