Skip to main content
NetApp Knowledge Base

What happens when Object Store access is interrupted for FabricPool?

Last Updated:

Applies to

  • StorageGRID
  • FabricPool
  • NFS
  • CIFS
  • SAN/Block Protocols


When connectivity between ONTAP and Fabricpool is interrupted, I/O will time out. The effect of I/O time outs is different per protocol.


  • NFS will return error message EJUKEBOX for v3 and EDELAY for v4.x.
  • NFS clients will retry after 5 seconds.
  • If it still gets the same error, NFS client will hang, until connection recovers.


  • CIFS will return STATUS_INTERNAL_ERROR to the client.
  • CIFS does not retry on the error.
  • Each application can react differently.

SAN/Block Protocols:

  • If a block in the object store environment is required and remains unreachable for two minutes, a read error is returned to the host.
  • ONTAP volumes and LUNs will stay online
  • Host OS might flag the file system as being in an error state.


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.
Scan to view the article on your device