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.
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!