メインコンテンツへスキップ

CONTAP-349486: リブート後に FlexCache ボリュームに NFS 経由でアクセスできない

Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

問題

  • リブート後、FlexCacheボリュームはNFS経由でアクセスできなくなります
  • Originボリュームにはアクセスできます
  • Originボリュームがあるノードのsktracesには以下のメッセージが表示されます
    • WAFLREMOTE_EXCEPTION:  Failing retrieve for origin 1051.5705393 with ERETRY because cache vol-msid: 2149588280 is fenced pending NIX
    • WAFLREMOTE_EXCEPTION:  NIX Mgr completed with status fail (3002)
      • SPINNP_ERR_FLEXCACHE_CONFIG_STALE = 3002, // FlexCache config APIs returned EFLEXCACHE_CONFIG_STALE
  • キャッシュを持つノードはEMSで次の内容が表示されます
    • Nblade.JunctionRootLookup2: Junction root lookup failed for a volume (Name: <flexcache volume name>, MSID: <flexcache volume MSID>) in Vserver (Name: <flexcache vserver>, ID: <flexcache vserver ID>) with reason: SPINNP(292)
      • SPINNP_ERR_RETRY = 292,       // General-purpose retry error code

  • kernel: Nblade.dBladeNoResponse.NFS:error]: File operation timed out because there was no response from the data-serving node. Node UUID: <node UUID>, file operation protocol: NFS, client IP address: <client IP>, Opcode/Procedure: NFS3_LOOKUP(3).

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.