Dose FFS fragment an SD Card on your phone? Settings Recommendation…
I’ve set up the SFTP server on my android phone to use FFS. I currently have it set at 3 parallel operations with 3 channels. It would seem to make sense that it would possibly fragment the SD card a lot. Dose FFS safeguard against this in some way? Has anyone experienced any problems with a fragmented SD card using FFS? With the settings at 3/3 would it be fragmenting by 3 files or by 9?
Any recommendations as to settings for parallel operations and channels for an SD card on a phone are welcome.
(I am reorganizing my music library, just today I removed 8,000 files/folders and added 6 Gig’s to the SD card)
-Jaz
Does FFS fragment an SD Card on your phone? Settings Recommendation…
- Posts: 12
- Joined: 3 Sep 2025
- Posts: 4908
- Joined: 11 Jun 2019
Digital storage either always or never gets fragmented depending on how you look at it. Digital storage automatically wear-levels, which inherently fragments data. It doesn't matter though because seek times on digital storage are constant no matter where a block of data is stored, unlike mechanical drives.
For the other questions, multiple threads doesn't help unless there is an artificial limitation. Some servers do limit your connection speed so you can't impact other users, for example. Your SFTP server on Android very likely doesn't do this, so single thread is probably better actually. Your bottleneck is probably WIFI bandwidth.
Let's hypothetically say you were syncing to a mechanical drive, fragmentation depends on the algorithm the OS uses to write. There are many and it's something I learned in my 400-level OS class back in college. First fit, best fit, loose fit, etc. For end users, it isn't something you should even think about.
For the other questions, multiple threads doesn't help unless there is an artificial limitation. Some servers do limit your connection speed so you can't impact other users, for example. Your SFTP server on Android very likely doesn't do this, so single thread is probably better actually. Your bottleneck is probably WIFI bandwidth.
Let's hypothetically say you were syncing to a mechanical drive, fragmentation depends on the algorithm the OS uses to write. There are many and it's something I learned in my 400-level OS class back in college. First fit, best fit, loose fit, etc. For end users, it isn't something you should even think about.
