Yes, from my point of view, there is a lot of things going on inside a SSD that is causing program writes to the NAND flash that is completely unrelated to Host Writes. E.g. For SMART, the SSD has to collect various data and regularly write that data to the disk. It has to calculate the power-on-hours, it has to measure temperature, it needs to backup the FTL and various other configuration status, ... the SSDs are logging a lot of stuff regularly in the SA. And not all of those writes are necessarily optimized for a WAF. Now usually (Data-Center, normal Desktop users) that isn't much compared to the Host-Writes. But in this scenario the user explicitly said that he isn't using the disk very much. So all those internal processes are likely far more in this scenario than normally, which accounts to an astronomic WAF. You can think of an SSD/HDD like a small computer inside the case of the SSD. And that computer does a lot of stuff, and therefore uses the NAND flash a lot. One thing for example is that SSDs are running background tasks like e.g. scanning for bad blocks and remapping them. There are no host writes for that, it's only running when the SSD is idle. So any regularly triggered SMART actions can likely stop those background tasks from running. I am not sure, whether holding off the SSD from doing those background tasks is a good idea. It could be, but it could also cause bigger troubles. -> Backup, backup, backup!
|