Limiting drive writes to the same area on the drive.

Started by wbennett, October 08, 2023, 07:54:36 PM

Previous topic - Next topic
Good day,

Just wondering how the logging retention affects the hard drive. I am currently keeping logs for seven days and I am not sure if, after the logs are flushed and a new seven day log starts, the same part of the drive is being written to for each seven day retention?

Thanks for any assistance.




UFS does not use copy on write. If you are worried about uneven drive wear because of logging you either need to switch to ZFS or configure a central logging server

Besides ... any particular reason why you are worried? Are you using an SSD as your boot drive? What's its TBW? Even with the same area written again and again the SSD controller usually will have your back. What you perceive as "the same area" in reality is far from it.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

Quote from: bartjsmit on October 09, 2023, 10:57:06 PM
UFS does not use copy on write. If you are worried about uneven drive wear because of logging you either need to switch to ZFS or configure a central logging server
Is the only way to switch to ZFS a complete reinstall?

Yes, but again, why are you worried? An SSD does not care if it's the same area or not. The manufacturer gurantees a certain number of terabytes written (TBW), regardless of the location. The controller creates an illusion of a certain capacity and certain fixed block addresses while spreading the wear over all cells all the time.

Look up the TBW value in your SSD's data sheet, compare with the actual number reported by smartctl -a ...
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

Quote from: Patrick M. Hausen on October 10, 2023, 12:04:25 AM
Yes, but again, why are you worried? An SSD does not care if it's the same area or not. The manufacturer gurantees a certain number of terabytes written (TBW), regardless of the location. The controller creates an illusion of a certain capacity and certain fixed block addresses while spreading the wear over all cells all the time.

Look up the TBW value in your SSD's data sheet, compare with the actual number reported by smartctl -a ...

IIRC, it's actually impossible to write to the same area with an SSD as the controller will straight out lie to you.