Sun ZFS Storage Appliance: SMB failures on ZFSSA on 2011.1

Asset ID:	1-72-1500509.1
Update Date:	2016-10-13
Keywords:

Solution Type Problem Resolution Sure

Solution 1500509.1 : Sun ZFS Storage Appliance: SMB failures on ZFSSA on 2011.1 - 2011.1.3

Applies to:

Sun ZFS Storage 7420 - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7120 - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7320 - Version All Versions to All Versions [Release All Releases]
7000 Appliance OS (Fishworks)

Symptoms

CIFS connectivity is interupted when running ZFSSA code 2011.1.1 to 2011.1.3. A restart of the SMB/CIFS service restores access.

Investigation of the logs shows the following messages in the /var/ak/logs/debug.sys

Jun 21 20:38:04 amberroad idmapd[1574]: [ID 455671 daemon.error] Check SMB service (svc:/network/smb/server).
Jun 21 20:38:04 amberroad idmapd[1574]: [ID 174421 daemon.error] Check connectivity to Active Directory.
Jun 21 20:38:04 amberroad idmapd[1574]: [ID 280452 daemon.error] Error:  smb_lookup_sid failed.
Jun 21 20:38:04 amberroad idmapd[1574]: [ID 455671 daemon.error] Check SMB service (svc:/network/smb/server).
Jun 21 20:38:04 amberroad idmapd[1574]: [ID 174421 daemon.error] Check connectivity to Active Directory.

The svc:/network/smb/server service log shows the following

smbd: smbd_dc_monitor: domain service not responding
smbd: smbd_door_dispatch: create failed: Resource temporarily unavailable
smbd: smbd_door_dispatch: create failed: Resource temporarily unavailable
smbd: Could not contact service: svc:/network/smb/client
smbd: smbd_door_dispatch: create failed: Resource temporarily unavailable
smbd: Could not contact service: svc:/network/smb/client
smbd: smbd_door_dispatch: create failed: Resource temporarily unavailable

Changes

Upgrading from older code can make this event possible. This event was not possible in any code older than 2011.1.0.

Cause

This event's cause is explained in CR 15804456

Solution

Upgrading to 2011.1.4 or higher will fix this issue. A restart of the SMB/CIFS service will provide a temporary workaround.

Attachments

This solution has no attachment