Sun ZFS Storage 7420
 
Oracle ZFS Storage ZS5-2
 
Oracle ZFS Storage ZS3-2
 
Oracle ZFS Storage ZS4-4
 
Oracle ZFS Storage ZS5-4
 
Oracle ZFS Storage ZS3-4
 
Sun ZFS Storage 7120
 
Sun ZFS Storage 7320
 

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

In this Document

Goal

Solution

References

Created from <SR 3-16615537750>

Applies to:

Goal

Customer is utilizing clone facility to propagate multiple shares across different projects.

Basically, they create a snapshot of a base share, that snapshot is then cloned multiple times to other projects.

As these are effectively snapshots, they don't show any space utilization when first created, but when mounted onto a target server, it can see the the data and therefore, how much space is in use.

Solution

When a snapshot of a share is taken, the snapshot does not contain all the data of the share but a reference point to what data was present in the base share when the snapshot was taken.

A clone is a writable copy of a snapshot and is treated as a new independent share.  A reference point uses a very small amount of space.

However when you export this to a server, it will read the contents hosted in the share. The reference points present in the share will direct the server to read the data from the base share.

If the base share has quota set to 100G and the same settings were retained to newly cloned share, you can copy data up to 100G to the clone.

This is because Storage see this as a new share with no data in it. It only has reference points to the data in the original share.

On the other hand if the quota settings were not retained on the clone, then data above 100G can be copied depending on the available space in the pool.

References

This solution has no attachment