メインコンテンツまでスキップ

ボリュームクォータサイズが変更されたあとにボリュームでクォータを作成できません

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

に適用されます

ONTAP 9

問題

  • ボリュームクォータサイズが変更されたあとにボリュームでクォータを作成できません。

例:

Cluster::> quota on -vserver svm -volume volname                               
Cluster::> quota status -vserver svm -volume volname 
        Vserver Name: svm
        Volume Name: volname
        Quota State: Quotas are initializing and transferring rules
Cluster::> quota status -vserver svm -volume volname 
        Vserver Name: svm
        Volume Name: volname
        Quota State: Quotas are off

  • EMS ログで、ユーザ名が見つからないために UNIX ユーザ検索が失敗したあとにクォータ処理の失敗を確認できます。
[nodename mgwd: mgmtgwd.jobmgr.jobcomplete.failure:info]: Job "Quota Operation" [id 10254] ("quota on" performed for quota policy "default" on volume "volname" in Vserver "svm") completed unsuccessfully: User name user1 not found. Reason: SecD Error: libc returned a transient error. Please look at the journal for detail. (1258185)
......
[nodename : secd: secd.unixLookupFailure:error]: vserver (svm) UNIX lookup failure. Error: Acquire UNIX credentials procedure failed
  [  1 ms] Successfully connected to ip 10.163.50.15, port 756 using TCP
  [    1] Unable to connect to NIS service on 10.163.50.15 (Error: Could not connect to server)
  [    1] No servers available for NIS, vserver: 11, domain: .
**[    1] FAILURE: Unable to make a connection (NIS:), result: 6940
  [    1] Source: NIS unavailable. Ignoring and trying next available source for user-name: user1
  [    2] Entry for user-name: chenj not found in the current source: FILES. Entry for user-name: user1 not found in any of the available sources
  [    2] Unable to retrieve UID for UNIX user user1
  • MGWD ログを使用すると、詳細な失敗の進行状況を確認できます。
[kern_mgwd:info:1684] 0x83725b600: 8603e900000133b0: ERR: VOPL::QuotaOps: JOB[10257]: pushRules: Cancel quota op after failure(User name user1 not found. Reason: SecD Error: libc returned a transient error. Please look at the journal for detail. ) from copy rules to zapi; retry count is 8

 

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.