this post was submitted on 17 Nov 2026
277 points (96.9% liked)
memes
23461 readers
1551 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
Makes sense thanks for taking the time.
not inodes but the ext2 FS itself.
XFS and BTRFS do need to be occasionally defragged if you use them on a single HDD (non RAID).
NTFS got away with never updating itself due to the introduction of SSDs, which is why Windows had to be aggressively defragged on HDDs starting from the Win 8 era onwards.
Thank you! <3
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.
Ext tries to avoid it by trying to keep space open in front of the write sector, or finding a space when it commits to disk rather than up front. If that fails the file gets fragmented. If you don't have a lot of space available on the disk it's more likely to happen (though this is the case on Windows as well for a slightly different reason. It's why Windows used to recommend that you leave at least 10% free space on the disk). Larger files obviously more likely to fragment as well.
I see, thanks!