Fragmentation is mostly a non-issue with ext2/3/4. If you’re filling drives to the brim with data usually accessed in sequence (a media library for example), you should still defrag occasionally to improve access times.
Edit: This assumes you’re using physical harddisks. SSDs are not negatively affected by data fragmentation in any way that functionally makes a difference.
inodes are just the id of a file entry on disk (e.g. NTFS has them, but calls them records)
There is still a need to defrag under *nix, but it’s just really uncommon because you’ll only get them when you update a file in-place, and most things don’t do that under *nix. So you’ll only see them in the common case with something like bittorrent downloads, and clients can still avoid that a lot of the time.
Did Linux ever defrag or do inodes make that irrelevant?
Fragmentation is mostly a non-issue with ext2/3/4. If you’re filling drives to the brim with data usually accessed in sequence (a media library for example), you should still defrag occasionally to improve access times.
Edit: This assumes you’re using physical harddisks. SSDs are not negatively affected by data fragmentation in any way that functionally makes a difference.
Ext2 and later made it irrelevant.
inodes are just the id of a file entry on disk (e.g. NTFS has them, but calls them records)
There is still a need to defrag under *nix, but it’s just really uncommon because you’ll only get them when you update a file in-place, and most things don’t do that under *nix. So you’ll only see them in the common case with something like bittorrent downloads, and clients can still avoid that a lot of the time.