That looks like it's probably just the result of APT (full-)upgrade running, tbh, or maybe the packages getting updated as a dependency of something else that was being installed at the time. The same modification time on related files fits with that simple explanation (e.g. the various files related to systemd were all 25-Aug-2024 21:05:15, and the files from the net-tools package were all 19-Aug-2024 16:30:00).
It's not wear levelling, assuming a standard install with an ext4 filesystem. The filesystem has no visibility at the block level of what wear levelling is going on inside a flash drive, and it certainly wouldn't update inodes/metadata; drives with wear levelling have an internal mapping table from logical blocks to physical blocks. Equally, the flash controller has no knowledge of filesystems or inodes, it just deals with blocks. That's for normal SD cards, SATA SSDs, and NVMe SSDs; where the OS just accesses them as a standard block device.
Have a look at /var/log/dpkg.log, you may well find the approximate modification times in there which match your observations (it might not be exact, as there could be a small time delta between file modification and logging).
It's not wear levelling, assuming a standard install with an ext4 filesystem. The filesystem has no visibility at the block level of what wear levelling is going on inside a flash drive, and it certainly wouldn't update inodes/metadata; drives with wear levelling have an internal mapping table from logical blocks to physical blocks. Equally, the flash controller has no knowledge of filesystems or inodes, it just deals with blocks. That's for normal SD cards, SATA SSDs, and NVMe SSDs; where the OS just accesses them as a standard block device.
Have a look at /var/log/dpkg.log, you may well find the approximate modification times in there which match your observations (it might not be exact, as there could be a small time delta between file modification and logging).
Statistics: Posted by Murph9000 — Fri Sep 13, 2024 3:54 pm