False Ext4 Corruption and Mount issue after Upgrading the Server
(Doc ID 2558145.1)
Last updated on APRIL 15, 2021
Applies to:Linux OS - Version Oracle Linux 6.9 and later
After updating the kernel and a few uptrack packages, and then rebooting the server, some ext4 filesytems are not getting mounted.
Attempts to mount the filesystem show filesystem corruption messages - but when running fsck it shows the filesystem is clean:
fsck.ext4 -f -y /dev/mapper/jiravg-jiralv
e2fsck 1.43-WIP (20-Jun-2013)
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
jira: 13441/25292800 files (1.0% non-contiguous), 3616744/104853504 blocks
The mount command shows filesystem as corrupted:
mount: wrong fs type, bad option, bad superblock on /dev/mapper/jiravg-jiralv,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
dmesg shows below:
11.300163] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts:(null)
[ 11.470630] EXT4-fs (dm-0): ext4_check_descriptors: Block bitmap for group
0 overlaps block group descriptors
[ 11.473873] EXT4-fs (dm-0): group descriptors corrupted!
[ 13.101854] Adding 2097148k swap on /dev/xvda3. Priority:-1 extents:1
The kernel version was upgraded to kernel-uek-4.1.12-124.26.12.
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