Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2262465.1
Update Date:2017-11-14
Keywords:

Solution Type  Problem Resolution Sure

Solution  2262465.1 :   Oracle ZFS Storage Appliance: Reboot "Unexpectedly found SAS zone locks held"  


Related Items
  • Sun ZFS Storage 7320
  •  
  • Oracle ZFS Storage ZS3-2
  •  
  • Oracle ZFS Storage ZS3-4
  •  
  • Sun ZFS Storage 7420
  •  
  • Oracle ZFS Storage ZS4-4
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
  •  




In this Document
Symptoms
Cause
Solution
References


Applies to:

Sun ZFS Storage 7320 - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7420 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS3-2 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS3-4 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS4-4 - Version All Versions to All Versions [Release All Releases]
7000 Appliance OS (Fishworks)

Symptoms

ZFS Array running code version AK 8.5.0 (2013.1.5.0) unexpectedly rebooted, but did not panic.

 

Examining akd.ak.txt at the time of the reboot you find:

Wed May 3 23:36:36 2017: Unexpectedly found SAS zone locks held

 

In jobs.txt you find:

[ Wed May 3 23:36:37 2017 /usr/sbin/uadmin "/usr/sbin/uadmin" "1" "1" ]

The above is the command that rebooted the system because the SAS zone lock sense was lost. This prevents a split brain condition.

 

Also the following is seen in the sas.ak.txt file:

Wed May 3 23:36:36 2017
nvlist version: 0
smp_errno = 0x7
smp_errmsg = engine library not found
errno = 0x6
message = NOLOCK found active ZM 504d435349455241
expander = (embedded nvlist)
nvlist version: 0
device_path = /devices/pci@0,0/pci8086,3410@9/pci11f8,8001@0/iport@f0/smp@w508002000148deff:smp
address = 0x508002000148deff
vendor = ORACLE
product = DE2-24C
revision = 0018
component_vendor = PMCSIERA
component_id = 0x8005
component_revision = 0x2
(end expander)

 

It was thought that forcing a crash dump rather than a reboot would provide more information on the cause of the zone lock issue.

But, anything that delays the reboot of this node runs the risk of inducing a split brain condition.

 

Cause

 Bug 24710575 - Unexpectedly found SAS zone locks held is currently in progress and cause will be supplied upon resolution.

 

Solution

Bug 24710575 has been closed as a duplicate of Bug 25532225 (SMP commands return more response data than the device supplied)

Fixed in Micro OS8.7.11 and later.

 

Upgrade to Micro OS8.7.11 or later.

 

References

<BUG:24710575> - UNEXPECTEDLY FOUND SAS ZONE LOCKS HELD

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback