I understood that XFS automatically mounted SSD’s with XFS_XFLAG_NODEFRAG set? Is this not the case?
I understood that XFS automatically mounted SSD’s with XFS_XFLAG_NODEFRAG set? Is this not the case?
That’s because the drive was written to its limits; the defrag runs a TRIM command that safely releases and resets empty sectors. Random reads and sequential reads /on clean drives that are regularly TRIMmed/ are within random variance of each other.
Source: ran large scale data collection for a data centre when SSDs were relatively new to the company so focused a lot on it, plus lots of data from various sectors since.
I do it regularly… I particularly like 4.
In all seriousness, I use it when I need to time something - 32 on one hand means one minute (approximately) with two rotations. I started when trying to determine if my daughter was asleep, waiting for a minute after she’d last moved or talked, and I didn’t want a screen or light or noise to wake her (she’s always been hard to get to sleep).
So - yeah it’s a tiny bit tricky to do some combos, but no more than touch typing.
According to the man(8) page, it will avoid touching any blocks that have the
chattr -f
flag set, which is XSR_XFLAGS_NODEFRAG… So I think if the docs are still accurate to the code, yes.A lot of ifs in that assumption.