对于NFSv4 StorePool问题、我应收集哪些数据?
适用场景
- ONTAP 9
- NFSv4.x
问题解答
- EMS消息提供了大量有助于缩小故障排除范围的信息
- 触发AutoSupport以提供此支持
- 记下 报告错误的节点的节点管理lf
- 统计信息提供了一些指导、用于查看是否有任何存储分段已满以及与哪些实例关联
- 什么是性能归档?它们是如何触发的?
- 统计信息start 可用于在一段时间内收集可多次引用的样本。
- 使用 REST API 调用检查
storePool_*
计数器:-
curl -siku "admin:PASSWORD" https://Cluster-Mgmt-IP/api/cluster/counter/tables/nfs_v4_diag/rows/
NOTE: use the response from above to run the second call per node to get the storePool counters like in example below.
示例:
curl -siku "admin: PASSWORD" https://Cluster-Mgmt-IP/api/cluster/counter/tables/nfs_v4_diag/rows/Cluster-01%3Cluster-01%3A67261b3
-
- 与存储池相关的对象
- NFSv4
- NFSv4_diag
- NFSv4_error
- NFSv4_1_error
- NFSv4_1_diag
- NFSv4_1
- sperror_error
- 发芽
- Spinhi
- lmgr_ng
- 从节点收集锁定以查看当前利用率(
vserver locks nfs4
在节点范围内)- vserver locks show 命令可用于查看存在哪些锁定
- 如果之前确定了一个顶级客户端、则在问题描述运行期间收集一个为该客户端筛选的数据包跟踪、并持续5分钟
- 如果已完成LIF迁移以缓解问题描述影响、请重新收集此数据。
- 请务必使用节点管理IP替换LIF当前所在的节点。
追加信息
- NFSv4存储池—解决方案指南
-
[1]我们提供了一个bash脚本、以便于更轻松地收集此数据
#!/bin/bash #Set the IP address of the node management server NODE_MANAGEMENT="NODE-MGMT-IP" # NODE_MANAGEMENT="10.2.1.3" #Set the username to user during authentication (Ideal to use pubkey auth) USERNAME="admin" #Create a directory to store the statistics mkdir -p statistics/$NODE_MANAGEMENT #Collect the statistics for NFSv4 and NFSv4_1 for version in nfsv4 nfsv4_1 do for TYPE in "" "_diag" "_error" do ssh $USERNAME@$NODE_MANAGEMENT "set d -c off; rows 0; date; statistics show -object $version$TYPE -raw" >> statistics/$NODE_MANAGEMENT/nfs.txt done done #Collect the statistics for spinnp for TYPE in spinnp_error spinhi spinnp do ssh $USERNAME@$NODE_MANAGEMENT "set d -c off; rows 0; date; statistics show -object $TYPE -raw" >> statistics/$NODE_MANAGEMENT/spin.txt done #Collect the statistics for lmgr_ng ssh $USERNAME@$NODE_MANAGEMENT "set d -c off; rows 0; date; statistics show -object lmgr_ng -counter files|hosts|owners|locks|*max -raw" >> statistics/$NODE_MANAGEMENT/locks.txt #Collect the statistics for vserver locks nfsv4 ssh $USERNAME@$NODE_MANAGEMENT "set d -c off; rows 0; date; vserver locks nfsv4 show -inst" >> statistics/$NODE_MANAGEMENT/locks.txt