Oracle ZFS Storage Appliance: How To Avoid LUN Mismatch When Using Replicated Luns to make a ZFS Pool on a Client
(Doc ID 1963940.1)
Last updated on JANUARY 31, 2022
Applies to:
Integrated Software for ZFS ZS3-x Arrays - Version All Versions to All Versions [Release All Releases]Sun ZFS Storage 7120 - Version All Versions to All Versions [Release All Releases]
Sun Storage 7410 Unified Storage System - Version All Versions to All Versions [Release All Releases]
Sun Storage 7310 Unified Storage System - Version All Versions to All Versions [Release All Releases]
Sun Storage 7210 Unified Storage System - Version All Versions to All Versions [Release All Releases]
7000 Appliance OS (Fishworks)
Symptoms
The Oracle ZFS Storage Appliance had three LUNs presented to a client host that were then used on that host as part of another ZFS pool.
All these LUNs had share level replication actions set on them and it was the replication copies of these LUNs that were used to make a ZFS pool on the client .
An issue occured such that the one of the replication actions got out of sync (or failed) . The result - on the client - was a ZFS pool that was incomplete because one LUN was out of sync with the rest.
To recover, the client host had to rebuild the ZFS pool from newly replicated copies.
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 |
| Cause |
| Solution |
| References |