3X0
Headphoneus Supremus
- Joined
- Sep 2, 2006
- Posts
- 3,963
- Likes
- 129
The (oversimplified) way I've always seen it is that FAT32 and NTFS storage systems allocate data as such:
HEAD-FI.ORG
This means that if files were to grow or move, fragmentation would likely result.
While a file system such as ext3 (Linux/Unix) allocates data as such:
H E A D - F I . O R G
As such there is ample overhead for the movement of files and active file size increase without unnecessary fragmentation.
I can't really speak for MFS/HFS/HFS+ that's used for Macintosh devices. I've never had experiences with one.
In most cases defragmenting a player would pose infinitesimal benefit; perhaps it might make the most fragmented of players a tiny bit speedier in accessing the disk or perhaps save a small amount of battery life.
Despite this, I make it an obsessive-compulsive habit to defragment my iAudio X5L every time I change files on it. Only takes me about five to ten minutes for about 28GB of data.
It has a high risk of messing up players that aren't UMS drag-and-drop, I imagine.
HEAD-FI.ORG
This means that if files were to grow or move, fragmentation would likely result.
While a file system such as ext3 (Linux/Unix) allocates data as such:
H E A D - F I . O R G
As such there is ample overhead for the movement of files and active file size increase without unnecessary fragmentation.
I can't really speak for MFS/HFS/HFS+ that's used for Macintosh devices. I've never had experiences with one.
In most cases defragmenting a player would pose infinitesimal benefit; perhaps it might make the most fragmented of players a tiny bit speedier in accessing the disk or perhaps save a small amount of battery life.
Despite this, I make it an obsessive-compulsive habit to defragment my iAudio X5L every time I change files on it. Only takes me about five to ten minutes for about 28GB of data.
It has a high risk of messing up players that aren't UMS drag-and-drop, I imagine.