Exadata: How to Clean Warning "EXT4-fs (dm-0): Initial Error" on Root Partition
(Doc ID 2523776.1)
Last updated on MAY 26, 2020
Applies to:
Linux OS - Version Oracle Linux 6.0 and laterLinux x86-64
Goal
Below warning messages are reported on root partition repeatedly:
Feb 9 19:58:44 hostname kernel: EXT4-fs (dm-0): error count: 394
Feb 9 19:58:44 hostname kernel: EXT4-fs (dm-0): initial error at 1549707482: ext4_ext_remove_space:2572: inode 1186259
Feb 9 19:58:44 hostname kernel: EXT4-fs (dm-0): last error at 1549708960: ext4_mb_generate_buddy:757
The above warning messages still keep being reported after running fsck in rescue mode using diagnostic ISO image successfully as below:
-sh-4.1# fsck.ext4 -f -y /dev/mapper/VGExaDb-LVDbSys1
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
DBSYS: 106220/1966080 files (1.4% non-contiguous), 4383863/7864320 blocks
The purpose of this document is to provide steps about how to clean these warning messages on Exadata server.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |