Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 16 results
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Are_quotas_based_on_Windows_group_IDs_supported
      If you specify a Windows group ID as the quota target, the quota is considered to be a user quota. Customers who need this feature can open a Support ticket to have the case added to the request. Note...If you specify a Windows group ID as the quota target, the quota is considered to be a user quota. Customers who need this feature can open a Support ticket to have the case added to the request. Note: The technical ticket only serves the purpose of adding the request and case ID to the RFE. Customers needing an update on the status of the RFE and/or would like to drive it forward as a matter of urgency, please engage your Account Team or Sales Representative to do so.
    • https://kb.netapp.com/data-mgmt/AIQUM/AIQUM_Kbs/Timeout_loading_volume_list_when_creating_a_qtree_or_quota_in_System_Manager_9.8
      Applies to OnCommand System Manager (SM) 9.8 Issue Timeout when entering the volume name in order to search for a volume when creating a quota or qtree in SM 9.8 The volume will not be found Sometimes...Applies to OnCommand System Manager (SM) 9.8 Issue Timeout when entering the volume name in order to search for a volume when creating a quota or qtree in SM 9.8 The volume will not be found Sometimes the scroll bar would hang and you would not be able to scroll down on the dropdown menu
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/How_Quotas_display_with_NFS_clients_df_output
      In the above example of 20G volume, a disk quota limit of 1G is set for both Windows user RTP2K8DOM2\jsiva and Unix user ID 5839 for qtree called home. If the qtree has NTFS security style and if the ...In the above example of 20G volume, a disk quota limit of 1G is set for both Windows user RTP2K8DOM2\jsiva and Unix user ID 5839 for qtree called home. If the qtree has NTFS security style and if the CIFS user maps the qtree, then the mapped drive will be 1G in size under Windows. However on UNIX, the NFS mount of the qtree will still show the full size of the volume when a user quota is set. And rquota must be enabled on the controller side to check the user quota from the NFS client.
    • https://kb.netapp.com/on-prem/ontap/Perf/Perf-KBs/High_latency_observed_on_volume_with_quotas_enabled
      High Write or Other latency on a volume with quota enabled. [node1: wafl_exempt13: quota.exceeded:debug]: params: {'ltype': 'hard', 'limit_value': '1024000', [node1: wafl_exempt02: wafl.quota.userQtre...High Write or Other latency on a volume with quota enabled. [node1: wafl_exempt13: quota.exceeded:debug]: params: {'ltype': 'hard', 'limit_value': '1024000', [node1: wafl_exempt02: wafl.quota.userQtree.exceeded.win:notice]: tid 2: disk quota exceeded on volume Additional warnings will be suppressed for approximately 60 minutes or until a 'quota resize' is performed.
    • https://kb.netapp.com/data-mgmt/AIQUM/AIQUM_Kbs/Active_IQ_Unified_Manager_quota_email_notifications_are_missing_SVM_in_generated_output
      Applies to Active IQ Unified Manager 9.7+ ( AIQUM ) Issue On the Active IQ Unified Manager (AIQUM) "Quota Email Format" page, "Email Details" are configured to use the $QUOTA_TARGET variable. Using th...Applies to Active IQ Unified Manager 9.7+ ( AIQUM ) Issue On the Active IQ Unified Manager (AIQUM) "Quota Email Format" page, "Email Details" are configured to use the $QUOTA_TARGET variable. Using the "Preview" button to see an example shows that $QUOTA_TARGET should resolve to SVM:/volume/qtree format, but in the actual emails received the SVM is omitted. Example Email Details This is the $QUOTA_TARGET Expected (in preview) vserver1:/volume1/qtree1 Actual (in email) /volume1/qtree1
    • https://kb.netapp.com/Legacy/OnCommand_Suite/Quota_email_notification_doesn_t_work_in_OnCommand_Unified_Manager_when_quota_type_is_QTREE
      Applies to Active IQ Unified Manager (AIQUM) 9.6+ All OS versions Quota email rules Issue Quota email notification doesn't work in Unified Manager when quota type is QTREE
    • https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/DF_shows_more_used_capacity_compared_to_quota_report
      svm Vol1 2305843013508661248 1.15TB svm Vol1 2305843017803628544 188.0GB svm Vol1 2305843022098595840 5.80TB svm Vol1 2305843026393563136 1012GB svm Vol1 2305843030688530432 440.9GB svm Vol1 230584303...svm Vol1 2305843013508661248 1.15TB svm Vol1 2305843017803628544 188.0GB svm Vol1 2305843022098595840 5.80TB svm Vol1 2305843026393563136 1012GB svm Vol1 2305843030688530432 440.9GB svm Vol1 2305843034983497728 0B svm Vol1 2305843039278465024 171.5GB svm Vol1 2305843043573432320 349.5GB svm Vol1 2305843052163366912 122.2GB svm Vol1 2305843056458334208 299.1GB svm Vol1 2305843060753301504 0B svm Vol1 2305843065048268800 57.90GB svm Vol1 2305843073638203392 540.2GB svm Vol1 2305843077933170688 0B
    • https://kb.netapp.com/hybrid/StorageGRID/Object_Mgmt/Can_Storage_Usage_exceed_its_Quota_for_StorageGRID_S3_Swift_tenants
      Yes, Storage Usage of S3/Swift tenants can exceed their Quota in some situations If quota check is not exceeded at start of object upload: Upload will succeed, even if other objects whose size meet th...Yes, Storage Usage of S3/Swift tenants can exceed their Quota in some situations If quota check is not exceeded at start of object upload: Upload will succeed, even if other objects whose size meet the quota are being processed Storage Usage can exceed its Quota after all uploads are complete If quota check is exceeded at start of object upload: Contact your StorageGRID administrator to increase the limit.}, Details={Logical bytes limit of 8000000000 exceeded.
    • https://kb.netapp.com/hybrid/StorageGRID/Object_Mgmt/StorageGRID_Object_store_for_Fabricpool_unavailable_briefly
      Applies to StorageGRID FabricPool Ontap logs EMS message that object store is unavailable: [Node-01: OscLowPriThreadPool: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "Fa...Applies to StorageGRID FabricPool Ontap logs EMS message that object store is unavailable: [Node-01: OscLowPriThreadPool: object.store.unavailable:EMERGENCY]: Unable to connect to the object store "Fabricpool_01" from node XXXXXXXXXXXXXX. A second later, this is followed by an EMS message that the object store is available again: [Node-01: OscLowPriThreadPool: object.store.available:notice]: Able to connect to the object store "Fabricpool_01" from node XXXXXXXXXXXXXX. No impact is reported.
    • https://kb.netapp.com/Legacy/ONTAP/7Mode/Quota_resize_returns_message_skipping_new_definition
      Applies to ONTAP 9 Issue Quotas are enabled and working correctly. However, running a quota resize returns error messages similar to the following: Example: Wed Oct 17 10:27:54 MEST [data02: quota.par...Applies to ONTAP 9 Issue Quotas are enabled and working correctly. However, running a quota resize returns error messages similar to the following: Example: Wed Oct 17 10:27:54 MEST [data02: quota.parse.error:error]: quota: skipping new definition for /vol/vol2/AAA (/etc/quotas line 136). Wed Oct 17 10:27:54 MEST [data02: quota.parse.error:error]: quota: skipping new definition for /vol/vol2/XYZ (/etc/quotas line 137).
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/NFS_client_gets_the_error_Operation_not_permitted_when_runing_the_command_quota_s_v
      NFS client gets the error "Operation not permitted" when running the command "quota -s -v" NFS client gets below the error: [testuser@centos-04 quota1]$ quota -s -v quota: error while getting quota fr...NFS client gets the error "Operation not permitted" when running the command "quota -s -v" NFS client gets below the error: [testuser@centos-04 quota1]$ quota -s -v quota: error while getting quota from xx.xx.xx.xx:/d_83701/ for testuser (id 1004): Operation not permitted The vserver replies "EPERM" in the PKTT. 62 2020-11-05 12:29:40.329401 xx.xx.xx.xx xx.xx.xx.xx RQUOTA 146 V1 GETQUOTA Call (Reply In 63) For the QUOTA request we observe EPERM which is unexpected.