I'd like to attribute the FSCK to growing pains. Long story short we hit a few upper limits on a node at-capacity that we honestly never expected to hit that caused the node to seize and roll over, resulting in a FSCK that took way too long. Had a RAM issue on JAX02 the other day that resulted...