kernel: EXT4-fs (dm-13): mounted filesystem with ordered data mode
JBOD[5944]: Info: [monitor_one_media:229] ####### media monitor readbuf(null)
Oct 17 15:16:28 jf_js_bssfapp02 ntpd_intres[11500]: host name not found: 0.rhel.pool.ntp.org
Oct 17 15:16:28 jf_js_bssfapp02 ntpd_intres[11500]: host name not found: 1.rhel.pool.ntp.org
Oct 17 15:16:28 jf_js_bssfapp02 ntpd_intres[11500]: host name not found: 2.rhel.pool.ntp.org
Oct 17 15:16:28 jf_js_bssfapp02 ntpd_intres[11500]: host name not found: 3.rhel.pool.ntp.org
Oct 17 15:27:21 jf_js_bssfapp02 kernel: pa ffff880942f03a88: logic 64, phys. 26180800, len 64
Oct 17 15:27:21 jf_js_bssfapp02 kernel: EXT4-fs error (device dm-13): ext4_mb_release_inode_pa: free 55, pa_free 54
Oct 17 15:27:21 jf_js_bssfapp02 kernel: pa ffff880942f03f00: logic 64, phys. 26180736, len 64
Oct 17 15:27:21 jf_js_bssfapp02 kernel: EXT4-fs error (device dm-13): ext4_mb_release_inode_pa: free 55, pa_free 54
Oct 17 15:31:39 jf_js_bssfapp02 kernel: EXT4-fs error (device dm-13): ext4_mb_generate_buddy: EXT4-fs: group 11634: 28799 blocks in bitmap, 127 in gd
Oct 17 15:31:39 jf_js_bssfapp02 kernel: pa ffff8809c0ec36e0: logic 30720, phys. 381241344, len 2048
Oct 17 15:31:39 jf_js_bssfapp02 kernel: EXT4-fs error (device dm-13): ext4_mb_release_inode_pa: free 2048, pa_free 1
Oct 17 15:32:04 jf_js_bssfapp02 kernel: EXT4-fs error (device dm-13): ext4_put_super: Couldn't clean up the journal
Oct 17 15:32:23 jf_js_bssfapp02 kernel: EXT4-fs (dm-13): warning: mounting fs with errors, running e2fsck is recommended
Oct 17 15:32:23 jf_js_bssfapp02 kernel: EXT4-fs (dm-13): recovery complete
Oct 17 15:32:23 jf_js_bssfapp02 kernel: EXT4-fs (dm-13): mounted filesystem with ordered data mode. Opts:
Oct 17 15:32:31 jf_js_bssfapp02 ntpd_intres[11500]: host name not found: 0.rhel.pool.ntp.org
Oct 17 15:32:31 jf_js_bssfapp02 ntpd_intres[11500]: host name not found: 1.rhel.pool.ntp.org
Oct 17 15:32:31 jf_js_bssfapp02 ntpd_intres[11500]: host name not found: 2.rhel.pool.ntp.org
Oct 17 15:32:31 jf_js_bssfapp02 ntpd_intres[11500]: host name not found: 3.rhel.pool.ntp.org
Oct 17 15:48:34 jf_js_bssfapp02 ntpd_intres[11500]: host name not found: 0.rhel.pool.ntp.org
Oct 17 15:48:34 jf_js_bssfapp02 ntpd_intres[11500]: host name not found: 1.rhel.pool.ntp.org
Oct 17 15:48:34 jf_js_bssfapp02 ntpd_intres[11500]: host name not found: 2.rhel.pool.ntp.org
Oct 17 15:48:34 jf_js_bssfapp02 ntpd_intres[11500]: host name not found: 3.rhel.pool.ntp.org
Responses
This Red Hat KB explains the reason why kernel logs that message : https://access.redhat.com/solutions/26413
As per these messages:
Oct 17 15:32:04 jf_js_bssfapp02 kernel: EXT4-fs error (device dm-13): ext4_put_super: Couldn't clean up the journal
Oct 17 15:32:23 jf_js_bssfapp02 kernel: EXT4-fs (dm-13): warning: mounting fs with errors, running e2fsck is recommended
it is better if you could run a complete file system check (e2fsck) on the next reboot. You could get this done on reboot by creating this file 'forsefsck' under root.
#cd /
#touch forcefsck
Once file system check is done on the next reboot this file (/forcefsck) would gets removed.
The above method would perform the file system check on all file systems as per /etc/fstab (provided if the last row bit is set to 2/1 for root, if it is 0 then it would be ignored). However, if you wish to get this done on a particular file system then this can be done as by setting the 'max-mount-counts' to 1 which could force file system on next reboot for a particular file system. Say for example, if it required to run a file system check only on root which is on lv '/dev/mapper/VolGroup/lv-root' then (remember it is not a good practice run file a complete system check on a healthy stack, as by default a quick check would be done on reboot to verify if journal is clean):
#tune2fs -c 1 /dev/mapper/VolGroup/lv-root
#reboot
After the file system check is done you would need to reset the 'max-mount-counts' back to either 0/1, otherwise, on each reboot file check would be forced. By setting the 'max-mount-counts' to either 0/1, kernel would ignore the number of times a file system gets mounted.
As per the man page of 'tune2fs':
-c max-mount-counts
Adjust the number of mounts after which the filesystem will be checked by e2fsck(8). If max-mount-counts is 0 or -1, the number of times the filesystem is mounted will be disregarded by e2fsck(8) and the kernel.
So, to reset this:
#tune2fs -c -1 /dev/mapper/VolGroup/lv-root
All the best!
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
