My Oracle Support Banner

Bug 32243513 ZFS Storage Appliance Writing One LUN (STMF) Property Clears the Other During Conversion (Doc ID 2890134.1)

Last updated on AUGUST 19, 2022

Applies to:

Enclave ZFS Block Storage ZS4-4 - Version All Versions and later
Oracle ZFS Storage ZS7-2 High End - Version All Versions and later
Oracle ZFS Storage Appliance Racked System ZS7-2 High-End - Version All Versions and later
Sun ZFS Storage 7320 - Version All Versions and later
Oracle ZFS Backup Appliance ZS5-4 - Version All Versions and later
7000 Appliance OS (Fishworks)
All ZFS Storage Appliance Products, Exceptions Noted Below.





Symptoms

Any LUNs created prior to applying the deferred update in 8.8.22 (Deferred Update: Improved LUN Attach and Detach Performance, Introduced in 2013.1.8.22 GA), within the range of versions affected, noted below, and where LUN properties were changed at some point after initial creation, would be susceptible to this issue.

In order for the symptoms to be triggered, some update to the LUN properties would have needed to occur, either by an administrative action or via a SCSI mode select from a client. Once that update occurs, the LUN properties are cleared and upon re-import (either by reboot or a restart of akd), the LUN would have default options applied. Initiatorgroup, targetgroup, assignednumber and status would be reset from the values the customer had previously set.

As long as the system is not rebooted or akd restarted, the kernel would still have the correct values for those properties and therefore, the system would continue to function without issue. However, viewing these properties (Initiatorgroup, targetgroup, assignednumber and status) via the ZFS Storage Appliance (ZFSSA) UI, would report those LUN properties as empty.

To identify and reinstate the previous LUN property values, please contact Oracle Support or open a new Service Request via My Oracle Support (MOS).

Please note: The above is a summary of the symptoms and actual symptoms can vary. Matching any symptoms here does not confirm that you are encountering this exact issue. For additional questions regarding this issue, please contact Oracle Support.

Changes

Issue Found In:

OS8.8.22, ak-2013.06.05.8.22

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.