Skip to main content
NetApp Knowledge Base

Why is there a delay in the output of the ls command on the origin side when the cache side is performing write operations?

  1. Last updated
    Apr 23, 2025
  2. Save as PDF
Views:
50
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:
4/23/2025, 9:32:24 AM

Applies to

  • ONTAP 9
  • FlexCache

Answer

  • In a write-back FlexCache environment, the data that newly saved to Cache should be transferred to Origin volume.
  • After running ls command, Origin waits the Cache to complete the new data transferring, it takes time.

Additional Information

  • While a write is occurring on the cache side, if the ls is executed on the origin, it will reclaim the delegation from the cache, causing it to wait until the write-back is complete.
  • At that time, even if another ls is executed on the cache side, the delegation is in the process of being reclaimed on the origin side, and since the ls command has not yet been executed on the origin, the cache side has no choice but to wait.
  • As a result, after the write-back is completed, the delegation is reclaimed on the origin side, and the ls command is executed there.
  • Afterwards, the delegation is passed back to the cache side, where the ls command is then executed.
  • Although it may appear that ls commands are being executed simultaneously, in reality, the origin executes first, followed by the cache.

 

 

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.