Sorry, I suppose my previous post was a bit unclear
. I'm pretty sure there was an error in your filesystem. This can happen when you move your clock around for DST for instance, because the FS sees writes that have occured 'in the future'. This can also happen for other reasons (your computer crashed, et cetera). This probably won't get logged in any system log (save for maybe a kernel log, but I'm not sure... the kernel logs can be a scary place) because your syslogger wasn't started when the error occurred (I'm fairly sure the FS is checked before any daemons are started). Regardless, there is no need to worry about this error. fsck fixed the error (which was why it rebooted), and unless you have any lost data or unmountable partitions, you can sleep easy.