Node : linux.setaoffice.com
Node Type : Intel/AMD x64(HTTPS)
Severity : minor
OM Server Time: 2017-12-29 15:04:09
Message : EXT4-fs: : Can’t allocate: Allocation context details:
Msg Group : OS
Application : dmsg_mon
Object : EXT4
Event Type :
not_found

Instance Name :
not_found

Instruction : No
EventDataSource :

This problem happens because there is a filesystem nearly full

root@linux:~ # df -hP /osprov
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg01-ospvol 405G 379G 4.4G 99% /osprov

root@linux:~ # vgs vg01
VG #PV #LV #SN Attr VSize VFree
vg01 1 4 0 wz–n- 599.88G 11.25G

Checking the logs, I discovered that the device being affected is a snapshot from a filesystem

root@linux:/var/log # zgrep “Can’t allocate: Allocation context details” messages* | grep -v CMD
messages.1.gz:Dec 8 20:00:16 linux kernel: EXT4-fs: Can’t allocate: Allocation context details:
messages.1.gz:Dec 29 20:00:17 linux kernel: EXT4-fs: Can’t allocate: Allocation context details:
messages.2.gz:Nov 10 20:00:17 linux kernel: EXT4-fs: Can’t allocate: Allocation context details:
messages.2.gz:Nov 24 20:00:17 linux kernel: EXT4-fs: Can’t allocate: Allocation context details:

Getting ” EXT4-fs: Can’t allocate: Allocation context details” errors in logs while using ext4 with Red Hat Enterprise Linux 5.6 and higher

I’ve added message to file /var/opt/OV/conf/OpC/dmsg_mon.cfg to ignore this alarm

root@linux:/var/opt/OV/conf/OpC # vi dmsg_mon.cfg
EXT4-fs: Can’t allocate: Allocation context details

• Linux