File system fragmentation: Difference between revisions

Content deleted Content added
reference dead link (404), update it to new ___location
Remove "unlimited fragmentation" statement from lead paragraph. Hitting a limit of fragmentation is not a widespread problem; even if it is true for some FSes in some edge cases, I don't think it deserves space in the lede.
Line 1:
[[File:FragmentationDefragmentation.gif|thumb|Visualization of fragmentation and then of defragmentation]]In [[computing]], '''file system fragmentation''', sometimes called '''file system aging''', is the tendency of a [[file system]] to lay out the contents of [[Computer file|files]] non-continuously to allow in-place modification of their contents. It is a special case of [[fragmentation (computer)#Data fragmentation|data fragmentation]]. File system fragmentation increases disk head movement or [[seek time]] (where it applies), which are known to hinder [[throughput (disk drive)|throughput]]. In addition, file systems cannot sustain unlimited fragmentation. The correction to existing fragmentation is to reorganize files and free space back into contiguous areas, a process called [[defragmentation]].
 
In computers with [[solid-state drives]], file system fragmentation is much less of a performance problem, as there is no movement of heads or discs. In fact, defragmenting such drives can slowly shorten their lifespan.