Tales From The Geek Side

(This tip provided by John Ghidiu)
Sometimes evolution will be out of sync with the exchange server. As I write this it’s a known problem. The workaround is to force evolution to shutdown and then force it to rebuild the local folder cache.

It seems that Evolution getting out of sync with Exchange is an old, old bug. If you run:

evolution –force-shutdown
rm -rf ~/.evolution/exchange//folders.db (this is the cache, I think)

and then start Evolution again, things work again.

My file server appeared to have some filesystem issues. I wanted to check and repair the filesystem but I couldn’t find my system rescue CD on a USB stick. I considered rebooting the machine 30 times to force a check but that didn’t seem like a fun way to spend my time. The filesystem is the root filesystem and it is xfs which meant that I couldn’t use `tune2fs` to set the property to force a fsck.

Today I learned of a very easy way to force a file system check. That is to create a file /forcefsck. The startup scripts in the initial ramdisk will check the filesystem and remove the file.