Note: The “magical” tool for XFS is (obviously) xfs_repair. Having it running can sometimes be the tough issue.
Introduction
How could a filesystem corruption happen? There are a couple of likely causes to it:
Kernel bugs: they are infrequent but they also did happen many times in the past and will still happen in the future. Not many things to be done about them, other than applying patches / keeping the kernel up to date;
Memory issues, e.g. memory errors propagated to the file system in control structures: they are usually mitigated with ECC memory but they can never be ruled out;
Underlying storage issues: quite unlikely but nevertheless possible;
Using the reset button on running servers: journaling file systems are almost always able to recover from such incident;
RAID controller issues: this could be the leading cause and not be easy to mitigate, even if firmware upgrade is sometimes possible.
This is supposed to be a text about following your passion: some people follow on saving the world, others prefer apparently simpler things like popping green pigs. Don’t get me wrong: it’s not about the purpose per se but the way to get there. It’s always about work, a lot of work.
Looking at the screen below, one could easily conclude that – at some point – I did become very, very efficient in the pig popping business. At the end of the day, some of these golden eggs become available when winning 3 stars in maybe 60 different levels.
