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

In this Document

Symptoms

Cause

Solution

References

Created from <SR 3-12973008770>

Applies to:

Symptoms

A share on a customer's system went to Read Only mode.  The customer did not change it to Read Only.

There is evidence of the share (project) being changed back to Read Write in the alert log.

Sun Jul 10 16:58:50 2016
nvlist version: 0
address =
host =
annotation =
user =
class = audit.ak.appliance.nas.project.changeproperty
payload = (embedded nvlist)
nvlist version: 0
pool =
project =
property = readonly
oldvalue = 1
newvalue = 0
(end payload)

There is no evidence that anything was changed to Read Only, checking the alert logs and the zpool history.

Cause

In testing, RPE created a scenario where a project could be read only and a cloned snapshot of a read/write share from a replication was be added to it.

That snapshot would then be read only within the project.

This is what most likely happened to this project/share.

This seems to be the only way that something like this could happen.

There is no evidence in the zpool history, or the alert log that the share in the read only project was made read only. These things would normally be logged.

Solution

There is no workaround or current fix available.

This is under investigation in Bug 24850368 - AKD auditing system fails to audit changes to replicated then cloned datasets

References

This solution has no attachment