Oracle ZFS Storage Appliance: Idmap database errors and smb_kdoor failures reported in the debug logs

Asset ID:	1-72-2188749.1
Update Date:	2017-05-11
Keywords:

Solution Type Problem Resolution Sure

Solution 2188749.1 : Oracle ZFS Storage Appliance: Idmap database errors and smb_kdoor failures reported in the debug logs

Related Items


Sun ZFS Storage 7420
 Oracle ZFS Storage ZS5-2
 Oracle ZFS Storage ZS3-2
 Oracle ZFS Storage ZS4-4
 Oracle ZFS Storage ZS5-4
 Sun ZFS Storage 7120
 Oracle ZFS Storage ZS3-4
 Sun ZFS Storage 7320
 Oracle ZFS Storage Appliance Racked System ZS4-4
 Oracle ZFS Storage ZS3-BA

Related Categories


PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS

In this Document

Symptoms

Cause

Solution

References

Created from <SR 3-13366625241>

Applies to:

Sun ZFS Storage 7420 - Version All Versions and later
Sun ZFS Storage 7320 - Version All Versions and later
Oracle ZFS Storage ZS3-2 - Version All Versions and later
Sun ZFS Storage 7120 - Version All Versions and later
Oracle ZFS Storage ZS3-4 - Version All Versions and later
7000 Appliance OS (Fishworks)

Symptoms

After the application for the fix for "Bug 21976688 - swap space limit exceeded error leading to loss of nfs service and idmap issues".

Idmap errors are still being reported. There are no more tmpfs errors or file system full messages

Sep 21 18:32:19 my_system idmap[28082]: [ID 469902 daemon.error] Database error on /system/volatile/idmap/idmap.db while executing
BEGIN TRANSACTION; (cannot start a transaction within a transaction)

Cause

Problem was caused by a lack of swap space corrupting the idmap database.

The fix for the swap problem was applied (Bug 21976688), but the idmap db was still corrupted.

Solution

Recycle idmap (restart the service) in configuration -> services -> idmap in the BUI.

References

<BUG:21976688> - SWAP SPACE LIMIT EXCEEDED ERROR LEADING TO LOSS OF NFS SERVICE AND IDMAP ISSUES

Attachments

This solution has no attachment