All of my servers in a multiserver setup have this or something close to it at around 6:30 or 7:00 am. Tried looking this error up but not getting a good answer. Does the first line mean that there are errors and need to do a fsck right away to fix this? Seems like all the servers have this and all are VM's. First time I've noticed that and do not know if this is normal on Debian Wheezy or not. Thanks! Sep 19 06:30:25 dotw275 kernel: [1124897.760040] EXT4-fs (dm-0): error count since last fsck: 12 Sep 19 06:30:25 dotw275 kernel: [1124897.760046] EXT4-fs (dm-0): initial error at time 1441536566: ext4_dirty_inode:4655 Sep 19 06:30:25 dotw275 kernel: [1124897.760051] EXT4-fs (dm-0): last error at time 1441537273: ext4_remount:4550 Sep 19 07:00:50 dotm371 kernel: [1124897.756024] EXT4-fs (dm-0): error count since last fsck: 11 Sep 19 07:00:50 dotm371 kernel: [1124897.756028] EXT4-fs (dm-0): initial error at time 1441536521: ext4_reserve_inode_write:4528 Sep 19 07:00:50 dotm371 kernel: [1124897.756031] EXT4-fs (dm-0): last error at time 1441537270: ext4_remount:4550
You can run a filesystem-check but this is not in all cases a "real fs-error". See https://lkml.org/lkml/2010/9/26/105
Thanks for the great info. Found a good Epoch & Unix Timestamp converter at http://www.epochconverter.com/ Helped me understand that these errors occurred weeks ago when I had some SAN issues and had to restart everything.
