0 Replies Latest reply on Jan 9, 2015 12:18 PM by kevinknox

    Adobe Media Encoder (Error compiling movie) Unknown error when writing to Isilon OneFS


      Adobe Media Encoder (Error compiling movie) Unknown error when writing to Isilon OneFS while using Adobe Premiere Pro.



      Process:         Adobe Premiere Pro CC 2014

      Path: /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014

      Identifier: com.adobe.AdobePremierePro

      Version:         8.1.0 (8.1.0)

      Code Type: X86-64 (Native)

      Parent Process: launchd [2538]

      Responsible:     Adobe Premiere Pro CC 2014


      Date/Time: 2015-01-06 14:04:23.500 -0700

      OS Version:      Mac OS X 10.9.2 (13C64)

      Report Version:  11



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


      Exception Type: EXC_BAD_ACCESS (SIGSEGV)

      Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000


      ****************************************************************************************** *****


      Customer created test export with 777 permissions and set mount parameters to the following:


      mount_nfs -o vers=3,tcp,rdirplus,intr,nolocks,async,rsize=32768,wsize=32768




        -- Original mount options:

           General mount flags: 0x40 async

           NFS parameters: vers=3,tcp,nolocks,rsize=32768,wsize=32768,rdirplus

        -- Current mount parameters:

           General mount flags: 0x4000058 async,nodev,nosuid multilabel

           NFS parameters: vers=3,tcp,port=2049,nomntudp,hard,nointr,noresvport,negnamecache,callumnt,nolocks,quota, rsize=32768,wsize=32768,readahead=16,dsize=32768,rdirplus,nodumbtimr,timeo=10,maxgroups=16 ,acregmin=5,acregmax=60,acdirmin=5,acdirmax=60,nomutejukebox,nonfc,sec=sys




      The pcap shows once the movie is created a lockup call is responded from Isilon with Error: NFS3ERR_NOENT



      478         V3 CREATE Call (Reply In 479), DH: 0xea5f731c/QBRSN-0-0-1.mov Mode: UNCHECKED

      479         V3 CREATE Reply (Call In 478)


      484         V3 LOOKUP Call (Reply In 485), DH: 0xea5f731c/._QBRSN-0-0-1.mov

      485        V3 LOOKUP Reply (Call In 484) Error: NFS3ERR_NOENT

      ****************************************************************************************** *********



      V3 LOOKUP Reply (Call In ....) Error: NFS3ERR_NOENT  -   This is by design of OneFS, we coalesce files and then flush them out to disk which is why the commit time is accurate but the file is not immediately available. however when an async option is used within the mount options this should be avoided if writing asynchronously to the cluster.  Has anyone else seen this behavior lately? (current workaround is to store locally and transfer to the cluster via Finder)