0007024: ext4: delayed block allocation failed with error -28

/var/log/message says below and no hardware related issues found.<br /> <br /> Mar 10 16:20:56 d02 auditd[4056]: Audit daemon rotating log files<br /> Mar 10 16:25:13 d02 kernel: EXT4-fs (sda): delayed block allocation failed for inode 47579238 at logical offset 395 with max blocks 1654 with error -28<br /> Mar 10 16:25:13 d02 kernel:<br /> Mar 10 16:25:13 d02 kernel: This should not happen!! Data will be lost<br /> Mar 10 16:25:13 d02 kernel: Total free blocks count 0<br /> Mar 10 16:25:13 d02 kernel: Free/Dirty block details<br /> Mar 10 16:25:13 d02 kernel: free_blocks=0<br /> Mar 10 16:25:13 d02 kernel: dirty_blocks=-4294772779<br /> Mar 10 16:25:13 d02 kernel: Block reservation details<br /> Mar 10 16:25:13 d02 kernel: i_reserved_data_blocks=1654<br /> Mar 10 16:25:13 d02 kernel: i_reserved_meta_blocks=7<br /> Mar 10 16:25:13 d02 kernel: EXT4-fs (sda): delayed block allocation failed for inode 58851678 at logical offset 0 with max blocks 2048 with error -28<br /> Mar 10 16:25:13 d02 kernel:<br /> Mar 10 16:25:13 d02 kernel: This should not happen!! Data will be lost<br /> Mar 10 16:25:13 d02 kernel: Total free blocks count 0<br /> Mar 10 16:25:13 d02 kernel: Free/Dirty block details<br /> Mar 10 16:25:13 d02 kernel: free_blocks=0<br /> Mar 10 16:25:13 d02 kernel: dirty_blocks=-4294772779<br /> Mar 10 16:25:13 d02 kernel: Block reservation details<br /> Mar 10 16:25:13 d02 kernel: i_reserved_data_blocks=2049<br /> Mar 10 16:25:13 d02 kernel: i_reserved_meta_blocks=7<br /> <br /> [<a href="mailto:root@d02">root@d02</a> ~]# uname -a<br /> Linux d02 2.6.32-358.11.1.el6.x86_64 <a href="http://bugs.centos.org/view.php?id=1">0000001</a> SMP Wed Jun 12 03:34:52 UTC<br /> 2013 x86_64 x86_64 x86_64 GNU/Linux<br /> <br /> [<a href="mailto:root@d02">root@d02</a> ~]# tune2fs -l /dev/sda<br /> tune2fs 1.41.12 (17-May-2010)<br /> Filesystem volume name: <none><br /> Last mounted on: /data/5aacbdff-697f-4b70-9b55-f912d41f57da<br /> Filesystem UUID: 5aacbdff-697f-4b70-9b55-f912d41f57da<br /> Filesystem magic number: 0xEF53<br /> Filesystem revision #: 1 (dynamic)<br /> Filesystem features: has_journal ext_attr resize_inode dir_index<br /> filetype needs_recovery extent flex_bg sparse_super large_file<br /> huge_file uninit_bg dir_nlink extra_isize<br /> Filesystem flags: signed_directory_hash<br /> Default mount options: (none)<br /> Filesystem state: clean<br /> Errors behavior: Continue<br /> Filesystem OS type: Linux<br /> Inode count: 183148544<br /> Block count: 732566646<br /> Reserved block count: 0<br /> Free blocks: 41810477<br /> Free inodes: 182809495<br /> First block: 0<br /> Block size: 4096<br /> Fragment size: 4096<br /> Reserved GDT blocks: 849<br /> Blocks per group: 32768<br /> Fragments per group: 32768<br /> Inodes per group: 8192<br /> Inode blocks per group: 512<br /> Flex block group size: 16<br /> Filesystem created: Fri Jul 5 10:11:15 2013<br /> Last mount time: Mon Jan 27 06:09:43 2014<br /> Last write time: Mon Jan 27 06:09:43 2014<br /> Mount count: 18<br /> Maximum mount count: 20<br /> Last checked: Fri Jul 5 10:11:15 2013<br /> Check interval: 15552000 (6 months)<br /> Next check after: Wed Jan 1 10:11:15 2014<br /> Lifetime writes: 6275 GB<br /> Reserved blocks uid: 0 (user root)<br /> Reserved blocks gid: 0 (group root)<br /> First inode: 11<br /> Inode size: 256<br /> Required extra isize: 28<br /> Desired extra isize: 28<br /> Journal inode: 8<br /> Default directory hash: half_md4<br /> Directory Hash Seed: e0d65199-15d8-4c39-aeeb-1d6cf3c6aebf<br /> Journal backup: inode blocks<br /> <br /> The number of dirty_blocks looks weird, is it a known bug?