跳转到主内容

卷接近全满、但LUN大小远远小于卷大小

Views:
6
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
san<a>2009年2009年</a>
Last Updated:

适用场景

  • ONTAP 9
  • LUN

问题描述

厚LUN大小 远远小于卷大小、但卷使用 量接近全满。
 

Cluster::> lun show -v

          Vserver Name: SVM1
            LUN Path: /vol/vol1/lun1
          Volume Name: vol1
           Qtree Name: ""
            LUN Name: lun1
            LUN Size: 3TB
            OS Type: windows_2008
       Space Reservation: enabled
         Serial Number: 80Bno]JZoKQQ
      Serial Number (Hex): 3830426e6f5d4a5a6f4b5177
            Comment:
   Space Reservations Honored: true
        Space Allocation: disabled
             State: online
            LUN UUID: 7745fafc-569f-4350-be0e-2377cf419707
             Mapped: mapped
Physical Size of Logical Block: 512B
        Device Legacy ID: -
        Device Binary ID: -
         Device Text ID: -
           Read Only: false
     Fenced Due to Restore: false
           Used Size: 2.01TB
      Maximum Resize Size: 15.97TB
         Creation Time: 11/28/2017 13:56:56
             Class: regular
      Node Hosting the LUN: JCTVNAS-02
        QoS Policy Group: -
   QoS Adaptive Policy Group: -
      Caching Policy Name: -
             Clone: false
    Clone Autodelete Enabled: false
      Inconsistent Import: false
          Application: -

 

 

Cluster::> vol show vol1 -instance

                  Vserver Name: SVM1
                   Volume Name: vol1
                 Aggregate Name: aggr1
  List of Aggregates for FlexGroup Constituents: aggr1
                 Encryption Type: none
        List of Nodes Hosting the Volume: Node-02
                   Volume Size: 5.09TB
               Volume Data Set ID: 1101
            Volume Master Data Set ID: 2151015477
                  Volume State: online
                  Volume Style: flex
              Extended Volume Style: flexvol
             FlexCache Endpoint Type: none
             Is Cluster-Mode Volume: true
              Is Constituent Volume: false
                  Export Policy: default
                     User ID: 0
                    Group ID: 0
                 Security Style: unix
                UNIX Permissions: ---rwxr-xr-x
                  Junction Path: -
              Junction Path Source: -
                 Junction Active: -
             Junction Parent Volume: -
                     Comment:
                 Available Size: 56.98GB
                 Filesystem Size: 5.09TB
             Total User-Visible Size: 5.09TB
                    Used Size: 5.03TB
                Used Percentage: 98%
      Volume Nearly Full Threshold Percent: 95%
          Volume Full Threshold Percent: 98%
                Maximum Autosize: 6TB
                Minimum Autosize: 5.09TB
       Autosize Grow Threshold Percentage: 95%
      Autosize Shrink Threshold Percentage: 50%
                  Autosize Mode: off
       Total Files (for user-visible data): 21251126
       Files Used (for user-visible data): 103
            Space Guarantee in Effect: true
               Space SLO in Effect: true
                    Space SLO: none
             Space Guarantee Style: volume
               Fractional Reserve: 100%
                   Volume Type: RW
        Snapshot Directory Access Enabled: true
       Space Reserved for Snapshot Copies: 0%
              Snapshot Reserve Used: 0%
                 Snapshot Policy: none
                  Creation Time: Tue Nov 28 13:56:55 2017
                    Language: C.UTF-8
                  Clone Volume: false
                    Node name: Node-02
            Clone Parent Vserver Name: -
             FlexClone Parent Volume: -
                  NVFAIL Option: on
              Volume's NVFAIL State: false
     Force NVFAIL on MetroCluster Switchover: off
            Is File System Size Fixed: false
           (DEPRECATED)-Extent Option: off
          Reserved Space for Overwrites: 2.01TB
        Primary Space Management Strategy: volume_grow
            Read Reallocation Option: off
   Naming Scheme for Automatic Snapshot Copies: create_time
        Inconsistency in the File System: false
          Is Volume Quiesced (On-Disk): false
         Is Volume Quiesced (In-Memory): false
    Volume Contains Shared or Compressed Data: false
        Space Saved by Storage Efficiency: 0B
     Percentage Saved by Storage Efficiency: 0%
          Space Saved by Deduplication: 0B
        Percentage Saved by Deduplication: 0%
          Space Shared by Deduplication: 0B
           Space Saved by Compression: 0B
      Percentage Space Saved by Compression: 0%
       Volume Size Used by Snapshot Copies: 10.23GB
                   Block Type: 64-bit
                Is Volume Moving: false
         Flash Pool Caching Eligibility: read-write
  Flash Pool Write Caching Ineligibility Reason: -
             Constituent Volume Role: -
              QoS Policy Group Name: -
         QoS Adaptive Policy Group Name: -
               Caching Policy Name: -
         Is Volume Move in Cutover Phase: false
     Number of Snapshot Copies in the Volume: 1
VBN_BAD may be present in the active filesystem: false
         Is Volume on a hybrid aggregate: false
            Total Physical Used Size: 2.02TB
            Physical Used Percentage: 40%
              Is Volume a FlexGroup: false
                  SnapLock Type: non-snaplock
              Vserver DR Protection: protected
                Enable Encryption: false
               Is Volume Encrypted: false
             Volume Encryption State: none
                Encryption Key ID:
                   Application: -
          Is Fenced for Protocol Access: false
           Protocol Access Fence Owner: -
                 Is SIDL enabled: off
              Over Provisioned Size: 0B
         Available Snapshot Reserve Size: 0B
                Logical Used Size: 5.03TB
             Logical Used Percentage: 99%
             Logical Available Size: -
     Logical Size Used by Active Filesystem: 5.02TB
       Logical Size Used by All Snapshots: 0B
             Logical Space Reporting: false
            Logical Space Enforcement: false
              Volume Tiering Policy: none
       Performance Tier Inactive User Data: -
   Performance Tier Inactive User Data Percent: -

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.
Scan to view the article on your device