Sun ZFS Storage 7420
 
Oracle ZFS Storage ZS3-2
 
Sun Storage 7110 Unified Storage System
 
Sun Storage 7210 Unified Storage System
 
Oracle ZFS Storage ZS4-4
 
Sun Storage 7410 Unified Storage System
 
Sun Storage 7310 Unified Storage System
 
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
 

PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: ZS
 

In this Document

Symptoms

Cause

Solution

Applies to:

Symptoms

Cloning a replicated project containing LUNs fails with:

error: Could not complete the action because LU number mapped to a selected
target/initiator group pair conflicts with LU numbers already assigned.
Prevent this error by removing access to the conflicting LUs.

Cause

For any given initiator group, no 2 LUNs can have the same LUN number.

When cloning a replicated project, the administrator has no control over the order in which the project's shares are cloned.

If the cloning order is such that a LUN with "lunumber=auto" is assigned LUN number 0 before the cloning of the LUN with "lunumber=0", we encounter a LUN number conflict and the project cloning operation fails.

Note: In the BUI "lunumber=auto" is called "LU POLICY Auto-assign".

Solution

Set all LUNs in the project on the replication source appliance to "lunumber=auto" and allow for the next replication update to complete before attempting again to clone the project.

To ensure that the current LUN numbers, including LUN number 0, remain the same throughout the lifetime of the LUNs, set "fixednumber=true" ("Persist" checkbox in the BUI).

The change from "lunumber=0" to "lunumber=auto" and setting "fixednumber=true" can be done online without any disruption.

This solution has no attachment