Quantcast
Channel: StudioSysAdmins Message Board
Viewing all articles
Browse latest Browse all 3749

Yosemite / BlueArc / SMB2.1 SMB3 kernel panics?

$
0
0
Yosemite / BlueArc / SMB2.1 SMB3 kernel panics?
posted by Jean-Francois Panisset on Jan. 14, 2015, 2 p.m. (1 day ago)
Is anyone else running into kernel panics on Macs running 10.10.1 talking SMB 2.1 or 3.0 to a BlueArc (running 11.3.3450.10 or .12)?

We used to get kernel panics in 10.9 running SMB 2.1, and were hoping that 10.10 would make things better, but clearly they haven't. Typical kernel crash dump stack trace:

Backtrace continues...
Kernel Extensions in backtrace:
com.apple.filesystems.smbfs(3.0)[5B6D27A4-5EF7-3C70-A440-0CE3ACC0DB1B]@0xffffff7f89e4a000->0xffffff7f89ea9fff
dependency: com.apple.kec.corecrypto(1.0)[0CB1D8BD-9EB7-3A02-8274-BCBB852B55B4]@0xffffff7f89da9000
dependency: com.apple.kext.triggers(1.0)[F2C2AFAA-0893-3FCF-84C6-09DBAC878952]@0xffffff7f89e45000

HDS says "we've never heard anyone else report this", so if someone else on this list is running into this, please report it to HDS so we can get some traction on getting this resolved?

Most likely the problem is on the OS X side (in theory, nothing the server returns should be able to cause a kernel panic), but I suspect that we may have more leverage with HDS?

JF

Thread Tags:
  discuss-at-studiosysadmins 

0 Responses   0 Plus One's   0 Comments  
 
Is anyone else running into kernel panics on Macs running 10.10.1 talking SMB 2.1 or 3.0 to a BlueArc (running 11.3.3450.10 or .12)?

We used to get kernel panics in 10.9 running SMB 2.1, and were hoping that 10.10 would make things better, but clearly they haven't. Typical kernel crash dump stack trace:

Backtrace continues...
Kernel Extensions in backtrace:
com.apple.filesystems.smbfs(3.0)[5B6D27A4-5EF7-3C70-A440-0CE3ACC0DB1B]@0xffffff7f89e4a000->0xffffff7f89ea9fff
dependency: com.apple.kec.corecrypto(1.0)[0CB1D8BD-9EB7-3A02-8274-BCBB852B55B4]@0xffffff7f89da9000
dependency: com.apple.kext.triggers(1.0)[F2C2AFAA-0893-3FCF-84C6-09DBAC878952]@0xffffff7f89e45000

HDS says "we've never heard anyone else report this", so if someone else on this list is running into this, please report it to HDS so we can get some traction on getting this resolved?

Most likely the problem is on the OS X side (in theory, nothing the server returns should be able to cause a kernel panic), but I suspect that we may have more leverage with HDS?

JF


Viewing all articles
Browse latest Browse all 3749

Trending Articles