On 29/01/11 23:33, Ted Ts'o wrote: > ... is strictly speaking not an error. It is a status report > indicating that in the past your file system had suffered an error. > The first error was at 1295177566 seconds past the epoch, or at: > > % date -d @1295177566 > Sun Jan 16 06:32:46 EST 2011 :; date -d @1295177566 Sun Jan 16 12:32:46 CET 2011 It's little later in my timezone and that was just after I resized my file system. > If you upgrade to e2fsck 1.41.14, it will reset the error counter and > the first/last most recent errors. I upgraded to 1.41.14, ran e2fsck and the messages have stopped. We still don't know what caused the initial errors (which have now vanished). As they started just after an online resize I'd guess that there were (are?) some bugs in that code. I'll avoid doing online resizes of my ext4 file systems for the moment. > The idea behind this is that > sometimes people aren't paying close attention to their > /var/log/messages file, so this is a periodic informational reminder, > printed once a day. That's a good idea. Once you know how to translate 1295177566 into a real time, you can go and look in the logs for the correct day. > If you are creating shell scripts to find errors, > match on "EXT4-fs Error", for example "EXT4-fs error (dm-28): disk on > fire". Warnings will be denoted with "EXT4-fs warning", and and > information messages, such as this one just start with "EXT4-fs", as > in "EXT4-fs (dm-28): ..." perhaps it would be better if they started with "EXT4-fs repeat message" (or something that you might be able to find with google) > Hope this helps, It sure does, thanks Stuart -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
