Filesystem choices

Bitpusher has made a strategic decision to begin recommending and using XFS in lieu of JFS in most cases. This is a tentative decision but also a significant shift, not one we take lightly.

We have had a pretty good but not great experience with JFS over the past 18+ months.

Now RedHat has shown movement towards official adoption of XFS (and also ext4) but not for JFS.

Our strategy must support the major Linux distros (most of our clients run CentOS, RHEL, Ubuntu or Debian), and since XFS and JFS are both equal “cousins” on the Debian/Ubuntu side of things it just makes sense to prefer XFS. ext4 is still a bit immature for our taste.

Furthermore, various performance benchmarks including this one generally give both high rankings
We will implement this strategy through attrition rather than by any kind of forced retrofit.

32-bit package cleanup

Red Hat and it’s variants have a nasty habit of installing 32-bit packages on a 64-bit platform like x86_64. See the output from uname -a to be sure, before proceeding.

Here is a one-liner that can be used (AT YOUR OWN RISK) to remove the offending packages. It has been my experience that this is generally safe to do.

rpm -qa --qf '%{name}-%{version}-%{release}.%{arch}n' | grep i.86$ | xargs rpm -e --nodeps

Also, adding this to /etc/yum.conf will prevent 32-bit packages from creeping back in.

exclude=kernel* *.i.86