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

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

In this Document

Symptoms

Changes

Cause

Solution

References

Created from <SR 3-17185138421>

Applies to:

Symptoms

This issue is often initially observed as a yellow problem indicator to the right of a share.

It may also be noticed by the share not presenting the expected data or being read-only.

After clicking on the yellow problem indicator, this error is reported:

In the Appliance CLI the following is reported for the problem share:

<errors> = mount_exists

Changes

Takeover performed.

Cause

When a ZFS Storage Appliance is active/active (AKCS_CLUSTERED) a replicated share can be exported even though a local share on the cluster peer uses the same mountpoint.

This often goes unnoticed until a takeover occurs.

After a takeover, both the replicated and local share with the same mountpoint are on the same ZFS Storage Appliance node.

Bug 15624084 (imported pools can obscure other share mountpoints) was closed as "not a bug" and working as expected.

It is up to the administrator to ensure duplicate mount points are not specified for shares.

Solution

Options to resolve the conflict:

• Stop exporting the replicated project containing the conflicting mountpoint.
• Change the mountpoint of the replicated project. e.g. from "/export" to "/export/replicated".  This will effect all replicated shares in that project.
• Change the mountpoint of the local share.

Various actions will need to be taken on the clients depending on the solution chosen, such as unmounting replicated shares or updating mount options to reflect new export names from the ZFS Storage Appliance.

References

This solution has no attachment