When I install EOS with btrfs(onluks), there is an added line in fstab to mount /tmp on tmpfs:
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
I though that was unnecessary (as per the wiki)
Do I miss something ?
Also, I see that the discard=async and ssd options are enabled, is that “better”?
So, no need of fstrim.timer anymore I assume? I thought I read somewhere that timer was “better” (less disk i/o and i.e. better lifespan) than discard unless you have To of data erased each day…
And I’m a bit confused with the ssd mount point as per the btrfs documentation
Note: Since 4.14, the block layout optimizations have been dropped. This used to help with first generations of SSD devices. Their FTL (flash translation layer) was not effective and the optimization was supposed to improve the wear by better aligning blocks. This is no longer true with modern SSD devices and the optimization had no real benefit. Furthermore it caused increased fragmentation. The layout tuning has been kept intact for the option ssd_spread.
P.S.: thank you so much for this wonderful distro guys!!!
But this is not from atlantis. I do that trim enabled for this drive but don’t know how you got that discard in yours though. If trim is there you don’t need discard. I also have the tmpfs mount which is pointed toward /tmp.
It is created by calamares, which isn’t Arch-specific.
The ssd option does nothing in this case since btrfs and Calamares use the same mechanism for detecting your ssd. However, it won’t hurt anything either.
discard=async is a performant way of doing discard/trim. It isn’t better or worse than the fstrim.timer in an absolute sense. It depends on your situation. Using both discard=async and the fstrim.timer is not necessary but it also won’t hurt anything. You will just get an extra trim operation once a week.
EDIT: I should probably point out that on my personal machines I don’t use discard=async and only use the fstrim timer.
That being said, feel free to alter any of those settings to meet your specific needs. You should look at the settings the installer provides as a best-effort starting point, not an absolute truth.