10.8.5 Update and FinalCut X (10.0.9)

matt321's picture

We are having issues since the 10.8.5 update with FinalCut X (10.0.9) randomly unmounting XSAN volumes.

Only rebooting the workstations fixes the issue.

Anyone having similar issues since updating?

abstractrude's picture

Wow, that is disturbing. When you say the volume, do you mean just on the client or in FCPX as an event volume? Elaborate a bit and share some logs.

-Trevor Carlson
THUMBWAR

matt321's picture

Here's what happens:

1. Boot Workstation, Login

2. Open FinalCut X

3. Add SAN Location...

4. About 5min in FinalCut tells me that the volume is no longer available.

5. Volume(s) disappear from the workstation and XSAN Admin (from the server) says it cannot connect to the client.

6. Reboot and it works for a few hours, then repeats the above.

We have 2 workstations and 2 MDCs, all running 10.8.5.

Working on getting some relevant logs.

matt321's picture

FinalCut Error:

Quote:
Process: Final Cut Pro [4698]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCut
Version: 10.0.9 (231027)
Build Info: ProEditor-23102007018000000~2
App Item ID: 424389933
App External ID: 15900113
Code Type: X86-64 (Native)
Parent Process: launchd [185]
User ID: 503

Date/Time: 2013-09-20 14:46:01.907 -0500
OS Version: Mac OS X 10.8.5 (12F37)
Report Version: 10

Crashed Thread: 88 Dispatch queue: com.apple.root.default-priority

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

/quote

XSAN (fsmpm) Error:

Quote:
Process: fsmpm [4718]
Path: /System/Library/Filesystems/acfs.fs/Contents/bin/fsmpm
Identifier: fsmpm
Version: 480.8
Code Type: X86-64 (Native)
Parent Process: xsand [65]
User ID: 0

Date/Time: 2013-09-20 14:45:56.779 -0500
OS Version: Mac OS X 10.8.5 (12F37)
Report Version: 10

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_ARITHMETIC (SIGFPE)
Exception Codes: EXC_I386_DIV (divide by zero)
/quote

Here is some of the System Log around when it crashes:

Quote:

Sep 20 14:45:57 VPMacPro1.local ReportCrash[4728]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
Sep 20 14:45:57 VPMacPro1.local ReportCrash[4728]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
Sep 20 14:45:57 VPMacPro1.local ReportCrash[4728]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
Sep 20 14:45:57 VPMacPro1.local ReportCrash[4728]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
Sep 20 14:45:57 VPMacPro1.local ReportCrash[4728]: Saved crash report for fsmpm[4718] version 480.8 to /Library/Logs/DiagnosticReports/fsmpm_2013-09-20-144557_VPMacPro1.crash
Sep 20 14:45:59 VPMacPro1.local xsand[65]: fsmpm exited on signal 8
Sep 20 14:45:59 VPMacPro1.local KernelEventAgent[88]: tid 00000000 received event(s) VQ_NOTRESP (1)
Sep 20 14:46:00 VPMacPro1 kernel[0]: Disconnected Porsche from FSS host 192.168.50.101
Sep 20 14:46:01 VPMacPro1.local mds[83]: XSANFS_FSCTL_SpotlightRPC fsctl failed (errno = 25)
Sep 20 14:46:01 VPMacPro1.local mds[83]: ERROR: _MDSChannelXsanFetchAccessTokenForUID: _XsanFetchAccessToken failed: 25
Sep 20 14:46:01 VPMacPro1.local mds[83]: (Error) Message: MDSChannel RPC failure (fetchQueryResultsForContext:) [no channelAccessToken]
Sep 20 14:46:01 VPMacPro1.local mds[83]: (Error) Store: {channel:0x7ff526c152e0 localPath:'/Volumes/Porsche'} MDSChannel failed -- initiating recovery
Sep 20 14:46:01 VPMacPro1.local mds[83]: XSANFS_FSCTL_SpotlightRPC fsctl failed (errno = 25)
Sep 20 14:46:01 VPMacPro1 kernel[0]: Un-mounted filesystem Porsche from FSM on host 192.168.50.101
/quote

What's weird is that we have Spotlight turned off on the volumes. And I have no idea how XSAN would "Divide by zero" but can't be good.

I will reapply the 10.8.5 update via the Combo Updater. Will report back it that fixes anything.

keithkoby's picture

I think we've seen similar in 10.8.4 with fcpx 10.0.9. So this might just be an fcpx issue.

matt321's picture

Here's a crazy one for you... The problem was the fault of Pioneer BluRay Drives (Specifically Pioneer BDR-208D).

For whatever reason FinalCut would dismount that drive and a few seconds later the XSAN volumes were dismounted and could only be re-mounted after a reboot.

Since disconnecting the BluRay drives we have had no issues with the XSAN volumes on the workstation.

Some observations:

-We only caught this because the XSAN volumes dismounted after we burned a DVD a few too many times (mind you the XSAN volumes dismounted even if we didn't burn a DVD)

-After the XSAN volumes were dismounted we could no longer control the BluRay drive. Sometimes it would disappear from the system, other times the BluRay drive still showed up but would not respond to eject or read commands.

-Every time the XSAN volumes crashed the "core" was rebuilt. This is some 17Gb file used by XSAN and is located in /cores. After crashing 10+ times it fills up the drive and the old/invalid "cores" had to be manually deleted.

10.8.5 supplemental update just came out and address an issue with drives unmounting, so that may be the culprit, but at the moment we have not tested that.

matx's picture

Do you still think it was the Pioneer Blu Ray drives causing the issues?

matt321's picture

Yes. As of today we have not experienced any crashing with the XSAN/Final Cut since disconnecting the BluRay Drives.

Two things:

1. We have not done the 10.8.5 supplemental update. This may fix the issue and allow us to reconnect the BluRay drives but we have been waiting for projects to slow down before we do that.

2. I have read a lot of places that similar issues are unique to Pioneer drives and that LG drives don't have as many problems. Had I known that beforehand we would have gone that route but we are not sure if the brand of the drive is actually the root of the problem.