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.
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 little fear is good ( lemmy.world )
Defragged Zebra ( sh.itjust.works )
We're in medieval Europe ( lemmy.world )
Weapons manufacturers are terrorist organizations ( lemmy.ml )
[Thread, post or comment was deleted by the author]