Redhat Server is showing file system error in messages file
HI Community,
while checking the messages file i found below alerts related to file system and it's reoccurring every day .
Apr 3 17:35:34 phcorc-gl kernel: EXT4-fs (sda2): error count: 18
Apr 3 17:35:34 phcorc-gl kernel: EXT4-fs (sda2): initial error at 1457527603: ext4_journal_start_sb:350
Apr 3 17:35:34 phcorc-gl kernel: EXT4-fs (sda2): last error at 1457531221: ext4_mb_generate_buddy:742
what is this error message about and it this critical. ? How can i fix this?
Regards,
Ben
Responses
Guru
6435 points
It means that you probably want to ensure that you have a known-good backup of /dev/sda2 ...possibly even all the partitions on /dev/sda. You've got filesystem grumph that could be coming from a number of places and you may be stuck having to do a full-fsck or even a nuke-and-restore to get back to a healthy state. Chances are, you've already got some degree of data-loss going on.
Might want to see if any hardware errors are getting captured in any other logs.
Community Member
70 points
HI Tom
Thanks for the reply.
this means i need to backup restore data to another disk? of hardware(disk) failure is going to happen?
Regards Ben
Community Member
70 points
HI
THis is running on vmware and i tried smartctl against that filesystem
smartctl --all /dev/sda smartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.8.13-16.2.1.el6uek.x86_64] (local build) Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
Vendor: VMware
Product: Virtual disk
Revision: 1.0
User Capacity: 134,217,728,000 bytes [134 GB]
Logical block size: 512 bytes
Device type: disk
Local Time is: Tue Apr 5 14:37:42 2016 AST
Device does not support SMART
Error Counter logging not supported Device does not support Self Test logging
Community Member
70 points
HI
i saw some article in another forum that
" This information (which is stored in the ext4 superblock) gets cleared by e2fsck version 1.41.13 or newer (1.41.14 is the most recently released version). If you are using an older version of e2fsck, this information won't get cleared, which is not a disaster, although it could potentially get annoying. The solution is to simply to upgrade to the newest version of e2fsprogs if you are using the 2.6.36 or newer kernel.
The idea behind this feature is to make sure that if there was a file system corruption detected, it wouldn't be lost due to log files getting overflowed. It's also helpful when users report problems to distribution support lines, since it makes it more likely support personnel will be able to determine that there has been some file system corrutpion issues, perhaps caused by hardware problems, or some other cause, including kernel bugs."
but while checking my e2fsprogs version,
rpm -qa|grep e2fsprogs e2fsprogs-1.42.8-1.0.1.el6.x86_64 e2fsprogs-libs-1.42.8-1.0.1.el6.x86_64
Community Member
70 points
HI David,
Thanks for your reply. Till now i don't get any proper solution/explanation for this.
Regards, Ben
Community Member
70 points
Hi Community,
any help on this. till now no one faced this issue?
Regards, Ben
Hi Ben, Were you able to resolve this? I am seeing the same issue on a device which serves the application from that file system. EXT4-fs (sddlmaa): error count since last fsck: 14 EXT4-fs (sddlmaa): initial error at time 1516387764: ext4_orphan_add:2586 EXT4-fs (sddlmaa): last error at time 1516398324: ext4_put_super:791 Thanks Suresh
Iam seeing these alrets for my server [606323.742864] EXT4-fs (sdj1): error count since last fsck: 6 [606323.742876] EXT4-fs (sdj1): initial error at time 1536083833: ext4_reserve_inode_write:4776 [606323.742881] EXT4-fs (sdj1): last error at time 1536083843: ext4_journal_check_start:56 [692898.463352] EXT4-fs (sdj1): error count since last fsck: 6 [692898.463365] EXT4-fs (sdj1): initial error at time 1536083833: ext4_reserve_inode_write:4776 [692898.463370] EXT4-fs (sdj1): last error at time 1536083843: ext4_journal_check_start:56 [779473.190108] EXT4-fs (sdj1): error count since last fsck: 6 [779473.190120] EXT4-fs (sdj1): initial error at time 1536083833: ext4_reserve_inode_write:4776 [779473.190125] EXT4-fs (sdj1): last error at time 1536083843: ext4_journal_check_start:56 [866047.917895] EXT4-fs (sdj1): error count since last fsck: 6 [866047.917907] EXT4-fs (sdj1): initial error at time 1536083833: ext4_reserve_inode_write:4776 [866047.917912] EXT4-fs (sdj1): last error at time 1536083843: ext4_journal_check_start:56 [952622.645894] EXT4-fs (sdj1): error count since last fsck: 6 [952622.645906] EXT4-fs (sdj1): initial error at time 1536083833: ext4_reserve_inode_write:4776 [952622.645911] EXT4-fs (sdj1): last error at time 1536083843: ext4_journal_check_start:56 [1039197.373078] EXT4-fs (sdj1): error count since last fsck: 6 [1039197.373090] EXT4-fs (sdj1): initial error at time 1536083833: ext4_reserve_inode_write:4776 [1039197.373095] EXT4-fs (sdj1): last error at time 1536083843: ext4_journal_check_start:56 [1125772.096717] EXT4-fs (sdj1): error count since last fsck: 6 [1125772.096729] EXT4-fs (sdj1): initial error at time 1536083833: ext4_reserve_inode_write:4776 [1125772.096735] EXT4-fs (sdj1): last error at time 1536083843: ext4_journal_check_start:56 [1212346.832344] EXT4-fs (sdj1): error count since last fsck: 6 [1212346.832356] EXT4-fs (sdj1): initial error at time 1536083833: ext4_reserve_inode_write:4776 [1212346.832362] EXT4-fs (sdj1): last error at time 1536083843: ext4_journal_check_start:56 [1298921.566695] EXT4-fs (sdj1): error count since last fsck: 6 [1298921.566707] EXT4-fs (sdj1): initial error at time 1536083833: ext4_reserve_inode_write:4776 [1298921.566713] EXT4-fs (sdj1): last error at time 1536083843: ext4_journal_check_start:56 [1385496.297667] EXT4-fs (sdj1): error count since last fsck: 6 [1385496.297679] EXT4-fs (sdj1): initial error at time 1536083833: ext4_reserve_inode_write:4776 [1385496.297685] EXT4-fs (sdj1): last error at time 1536083843: ext4_journal_check_start:56
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.