No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

eSight V300R010C00 Maintenance Guide 07

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ALM-316010204 inode Usage of the Disk Partition Is High

ALM-316010204 inode Usage of the Disk Partition Is High

Description

This alarm is generated when the inode usage of a specific partition exceeds 80%. On the Linux operating system, eSight runs the df -i command every 30 minutes to check the inode usage of each partition. This alarm can be automatically cleared if the inode usage of the partition is lower than or equal to 80%.

NOTE:

On the Linux operating system, inodes contain important information related to files in the file system. Each file has an inode.

Attribute

Alarm ID

Alarm Severity

Alarm Type

316010204

Critical

Environmental alarm

Impact on the System

Generally, about 1% of the file system disk space is allocated to inode tables. Therefore, inode resources that can be allocated in each partition are limited. If a large number of small files are created, inode resources will be used up, and new files cannot be created even if there is still available space.

Possible Causes

1. A large number of audit log files are created in the Oracle database. As a result, the inode usage of the partition where the Oracle database is located is too high.

2. A large number of small files are generated in a partition due to other reasons.

Procedure

Scenario 1: A large number of audit log files are created in the Oracle database. As a result, the inode usage of the partition where the Oracle database is located is too high.

  1. Log in to the server where the alarm is generated as the root user.
  2. Run the following command to check the mount point (for example, /opt) and inode usage (for example, the number of used inodes) of the disk partition (for example, /dev/sda10):

    #df -i /dev/sda10

  3. If the Oracle database directory (for example, /opt/oracle) is in this partition, run the following command to check the number of audit log files:

    #find /opt/oracle/ -type f -name "*.aud" | wc -l

  4. If the proportion of inode resources occupied by audit log files increases, the inode usage of the partition is too high, which is caused by the audit log files. Run the following command to invoke the audit log deletion tool of the Oracle database to delete the audit log files of the Oracle database:

    #su - oracle -c "/opt/oracle/product/11.2.0/db_1/bin/clean_audit_log.sh"

  5. Run the following command to check whether the inode usage of the partition corresponding to the Oracle database directory (for example, /opt/oracle) is lower than 80%:

    #df -i /opt/oracle/

Scenario 2: A large number of small files are generated in a partition due to other reasons.

  1. Log in to the server where the alarm is generated as the root user.
  2. Run the following command to check the mount point (for example, /home) and inode usage (for example, the number of used inodes) of the disk partition (for example, /dev/sda6):

    #df -i /dev/sda6

  3. Run the following command to check the distribution of small files (for example, files smaller than 1 KB) in the partition (for example, the mount point is /home):

    #find /opt -type f -size -1k

  4. If the files are useless, run the rm command to delete them in batches. If the files need to be stored, use the tar command to compress the file into a single file and then delete the original small files.
  5. Run the following command to check whether the inode usage of the disk partition (for example, /dev/sda6) is lower than 80%:

    #df -i /dev/sda6

Clearing

When the fault is eliminated, the system will automatically clear the alarm. Manual clearing is not required.

Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044373

Views: 25062

Downloads: 74

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next