OSX clients disconnect from Blue Arc Shares frequently..

Caffeine didn't work for us unfortunately.  6 of the 6 mac's it was installed on lost the connection overnight. ;(

-greg

On Tue, Jan 5, 2016 at 4:43 PM, greg whynott <greg.whynott@gmail.com> wrote:

I installed Caffine on the machines,  seemed the quickest thing to try,  will know tomorrow if it worked.

As for the SMB1 and 2,  I totally understand what and where they come from,  I was merely stating we tried both.  Slowness would of been acceptable if the disconnect issue went away,  but that wasn't the case.

I have concerns about both potential solutions ( new NIC,  sneaky sleep) as it is _only_ the HDS system that disconnects.    We have ISIS client,   TerraBlock client,   other windows shares hosted from both windows and non windows file servers,  yet only the HDS system disconnects its shares,   and that is the one in use for the transcoding.

I use to think it was our co-lo as this HDS server was across town,  but we recently moved it here on site and the problem persists...  

I so hope Caffine nails it.  ;)

thanks again Michael and Grant.

greg

On Mon, Jan 4, 2016 at 8:39 PM, <grantf@grunt.com.au> wrote:

Just a note on the 'sleep' issue. OSX will sleep even when background tasks are using 100% CPU and all power settings are set to never. I've struck this when putting MacPros onto a renderfarm. Even though the machine is rendering flat-out OSX will go into some sort of sleep mode and kill the render.

We solved it by installing an OSX app called Caffine (free from the AppStore). It puts up an icon of a coffee cup which when active (steaming) stops all screensaving/power/hibernation etc from happening.

Might be worth a test on a machine that's dropping while transcoding.

I also agree with Michael re SMB1 and SMB2. Apple dropped samba and wrote their own SMB code that want's to use SMB2.

 

 

On 2016-01-05 09:36, Michael Oliver wrote:

CIFS should be SMB1 where as SMB uses SMB2.  You might get slower speeds from SMB1 but at least you can narrow your problem down.  You can try forcing all smb connections to SMB1 via:

echo "[default]" >> ~/Library/Preferences/nsmb.conf; echo "smb_neg=smb1_only" >> ~/Library/Preferences/nsmb.conf

 

and/or try tweaking the "sysctl net.smb.fs" settings (increase loglevel, extend deadtimers)

 

Another thing I remember hearing about was some sort of issue with Apple NIC's and Cisco switches using certain configs.  Might be worth testing an Intel gigabit PCI-e card or USB3.0 Gb adapter to eliminate the NIC/switch issue.

 

Final guess...Maybe something with oplocks?

On Mon, Jan 4, 2016 at 2:12 PM, greg whynott <greg.whynott@gmail.com> wrote:

We have tried both Michael.   My understanding is CIFS is out in Apple land,  but I could be wrong there.  In any-event the behavior is about the same.  

 

The local apple store gave us a free 'enterprise support' call.  I'll give them a call,  for the second time in my life (first was back in the early 2000's during OSX's post beta days,   it was a worthless call and wasted money,  NFS issues,  the answer was "this is a known issue and should be fixed by the time your kid's kid's finish University,  or 37 years pass,  whichever comes first."

 

Google tells me others have the same issues with various SMB servers from OSX..  A few of them said they got around the problem by putting a AirPort between the client and server,  which of course is not a solution - and doesn't make a lot of sense, unless Apple didn't develop the OS/HW themselves...

 

-greg

 

 

On Mon, Jan 4, 2016 at 4:56 PM, Michael Oliver <mcoliver@gmail.com> wrote:

Are the clients mounting via smb:// or cifs://?  See if cifs gives you better stability.  

On Mon, Jan 4, 2016 at 10:32 AM, greg whynott <greg.whynott@gmail.com> wrote:

Hello everyone and happy nude rear.  ;)

 

 

We have about 20 OSX clients which mount SMB shares on our Blue Arc (running 12.3.3826.03c HDS code,  but the problem has been around for the last several upgrades).  The OSX client behavior is the same between versions 10.9 to current versions.

 

 

The video transcending group has been complaining about this for some time.   Over the Christmas break I set up a test on my mac (latest code).  It disconnected 11 times in 2 weeks.  The PC disconnected zero times during the same test period.   

The operators of the transcoding services claim these disconnects happen even when they are transcoding and cause the jobs to fail,  indicating it isn't a 'sleep' issue,  which by the way power savings is turned off.

 

Anyone else have experience with this issue? 

 

I'm going to collect a packet capture and attempt to trap it,  but thought I'd ask here at the same time.  

 

thanks much!

greg

 

 

 

 

  

 

 

 

To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe

 

--

Michael Oliver
mcoliver@gmail.com
858.336.1438

PGP Public Key: https://goo.gl/a2CnHF

To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe

To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe

 

--

Michael Oliver
mcoliver@gmail.com
858.336.1438

PGP Public Key: https://goo.gl/a2CnHF

To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe

To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe

To unsubscribe from the list send a blank e-mail to mailto:studiosysadmins-discuss-request@studiosysadmins.com?subject=unsubscribe