重新启动后无法通过 NFS 访问 Flexcache 卷
Knowledge Base guidance
This article may include metadata, visibility, validation state, and related support guidance.
适用场景
- ONTAP 9及更高版本
- Flexcache
- 原始卷是 SnapMirror 目标
问题描述
- 重新启动后，Flexcache 卷无法通过 NFS 访问
- 初始卷可访问
- 具有初始卷的节点将在sktraces中显示以下消息
WAFLREMOTE_EXCEPTION: Failing retrieve for origin 1051.5705393 with ERETRY because cache vol-msid: 2149588280 is fenced pending NIXWAFLREMOTE_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).