Skip to main content
NetApp Knowledge Base

SnapMirror stops transferring due to destination FabricPool aggr out of space

Last Updated:

Applies to

  • ONTAP 9
  • FabricPool
  • SnapMirror


  • Snapmirror relationships are created using System Manager and transfers work initially, but then fail with 'out of space' error
The "CLUSTERA" system only peers with one cluster called "CLUSTERB".  The relationships that replicate to that system are failing with error: (Failed to start transfer. (Filesystem error (No space left on device)))
  • The destination cluster aggregate is confirmed to be out space
cluster::> df -h
Aggregate               kbytes       used      avail capacity  
aggr0_n1             167651588  159527544    8124044      95%  
aggr0_n1/.snapshot     8823764          0    8823764       0%  
SSD_1               8626122096 8585980624   40141472     100%  
SSD_1/.snapshot              0          0          0       0%
  • The destination cluster aggregate uses FabricPool and the SnapMirror relationships on the source have 'all' set as tiering policy, so it was expected data would be automatically tiered off


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.