* More disk i/o done due to fragmented files in the small disk area.
* ALSO more cpu+memory work managing more seperate pointers in the fragmented file-allocation table.
* Defragmentation doesn't help and doesn't make sense with SSD disks.
In Windows and Linux as well as other OSs a full main disk will result in OS behaving slowly/badly in my experience.
Thoughts about this triggered by this question.
Why? Fragmentation on disk (and resulting increase of processing fragments in memory as well as number of disk read/writes). The remaining small area will be fragmented on disk, probably spread over different areas on disk. There is no space spare so de-fragmentation will not be able to help much until more space is freed up. All processes need to write temporary files (e.g. internet browser cache). These files will be fragmented. For magnetic disks the disk heads have to travel further which means slower file read/writes. For SSD disks I was not sure, this is a little bit boring but explains it well:
http://www.youtube.com/watch?v=VfYkJoqfG-k "Why Fragmentation is Still a Problem with SSDs". In memory (in file-allocation-table in memory) fragmented files take up more space and result in more cpu and bus activity dealing with different fragments. On the video he ends up with a sell for diskkeeper which is claims to improve the problem for SSDs. BUT allowing enough spare space on disk would probably be the best strategy.
This is good: Investigation into effect of de-fragging SSD.http://www.pcworld.com/article/2047513/fragging-wonderful-the-truth-about-defragging-your-ssd.htmlConclusion: There is no point in running a de-frag tool with SSD.
"There is limited benefit to reading data sequentially (beyond typical FS block sizes, say 4kB), making fragmentation negligible for SSDs. Defragmentation would cause wear by making additional writes of the NAND flash cells, which have a limited cycle life."
NOR and NAND Flash Memory Floating Gate