SAN Fusion 1.5.4 - Easily connect Avid Media Composer to an Xsan volume.

Note: Price available by phone or email. Visit the trial page for more information.

SAN Fusion is an easy and cost-effective solution that allows you to use Avid Media Composer with your existing Xsan infrastructure.

By using an existing Xsan volume as a backing-store for SAN Fusion's virtualized workspaces, editors can experience authentic Unity-style bin sharing and locking from within Media Composer 5.5.3 or later. Unlike other solutions that purport to make Avid work with Xsan, SAN Fusion is a client-side application with no additional server or minimum number of seats to buy.

SAN Fusion clients mount and unmount workspaces on demand through our intuitive GUI to provide Media Composer a real-time translation layer between it and Apple's Xsan filesystem. The end result is the best of both worlds: Avid's first class bin and media sharing combined with Apple's storage-agnostic low (or no) cost cluster filesystem.

File System:

• Fix issue when reading directory with many entries.
• When called with option "-o readdir_v2" the mounted sanfusefs volume will let libfuse manage readdir entries
• offset. This is a fallback in case the optimized VNODE_READDIR_EXTENDED mode fails

File System Driver (3.2.0 -> 3.3.2):

• Update libosxfuse to version 2.9.5
• Fix possible memory leak
• Minor under-the-hood clean up
• Disable CUSE support in libosxfuse


• The osxfuse kernel extension does not support the CUSE protocol.
• Send interrupt request on daemon timeout


• Send an interrupt request to give the file system daemon a chance to handle the timeout. If the daemon does not respond to the interrupt request within daemon_timeout seconds, the file system will be marked dead. Previous version of osxfuse deadened the volume right away without giving the daemon proper warning.


• This addresses issue osxfuse/osxfuse#261.
• Be more verbose in case vnop_readdir fails


• Finder and ls have the nasty habit of ignoring errors returned by vnode operation readdir. This might result in files missing from directory listings or directories appearing empty, even though they are not. One way to trigger this issue is returning a file name longer than 255 bytes in the the FUSE_READDIR callback. Starting with this release readdir errors are logged in system log.


• This addresses issue osxfuse/osxfuse#265.
• Change admin group from 80(admin) to 12(everyone). This allows non-admin users to use the allow_root and allow_other mount option.
• Update libosxfuse from version 2.9.5 to 2.9.6
• Bump number of FUSE devices to 64. Starting with this release 64 volumes can be mounted at the same time. Please note that depending on the file system and the used iosize, a single FUSE volume requires roughly 32 MB of RAM. 64 mounted FUSE volumes can require 2 GB of RAM.
• Lower minimum file system block size to 128 bytes
• Increase maximum file system block size from MAXPHYS (128 KiB) to MAXBSIZE (1 MiB)
• Clean up vnop_exchange operation in kernel extension to use only public API


• Use vnode_update_identity() instead of fuse_kludge_exchange() for updating the vnodes' names and parents.


• This renders fuse_kludge_exchange() obsolete.
• Implement new style mount process


• When mounting a FUSE volume on Linux, fusermount opens the FUSE device and passes the file descriptor back to libfuse.


• However, on OS X libosxfuse used to be responsible for locating a free FUSE device, opening it, and then passing the file descriptor to mount_osxfuse. For this to work libosxfuse needs to be aware of low level implementation details like the number of registered FUSE devices.


• In order to decouple libosxfuse from the FUSE kernel extension the mount process has been revised to match FUSE on Linux. mount_osxfuse will locate a free FUSE device, open it, and then pass the file descriptor back to libosxfuse.
• Update mount_osxfuse environment variablesL
• Remove unused MOUNT_FUSEFS_SAFE
• Rename MOUNT_FUSEFS_CALL_BY_LIB MOUNT_OSXFUSE_CALL_BY_LIB
• Remove unused FUSEDEVIOCSETIMPLEMENTEDBITS ioctl
• Optimize VNODE_READDIR_EXTENDED mode

• OS X 10.8.5 or later (including OS X 10.11)
• 8GB of RAM (16GB recommended)
• Xsan 3 or later, StorNext 4.2.1 or later, or NFSv3
• Media Composer 7.0.4 or later (including version 8.5)