fsck.xfs returns with status 0, so this step at boot is absolutely needless.

Only use fsck.mode=skip : if you use XFS file system.

Mitigations=off : improves performance but opens security risk, so you don't want to do that if you care about security.įor me though, no one is interested in getting into my system inside a private network :) If that's similar for you, turn off mitigation to make the system faster.

Use This Well-Tested Kernel Parameter (Also, Read the Warnings) GRUB_CMDLINE_LINUX_DEFAULT='fsck.mode=skip quiet loglevel=0 rd.systemd.show_status=false nowatchdog mitigations=off libahci.ignore_sss=1' But for thumb drives with OS installed, must use F2FS with -t option to disable TRIM (because a majority of thumb drives don't support TRIM). So you can go with XFS or F2FS for flash storages. I have been using XFS on both of my SSDs for a couple of years now, no problems.

It's the only file system dedicated exclusively for flash storages. They have garbage collection, TRIM, over-provisioning, etc. You see flash storages like SSD and thumb drives operates differently than traditional spinning HDDs. The RedHat's default file system is XFS.į2FS is created by Samsung for flash storages. XFS is a very robust journaling file system which is in servers. For thumb drive installation, F2FS with trim disabled. Here's how to set up your new installation to make it super fast: 1.

because those points make the look and feel different. That said, I won't be talking about installing lightweight WM/DE, etc. I have come up with some tricks to deliver the maximum performance from Arch Linux and most other distribution.

Arch linux process monitor