Originally Posted by
Ao1
Anvil I’m intrigued by this. AFAIK the SF controller is supposed to prevent the delta between the least-worn and most worn block from accumulating more than a few % of the maximum lifetime wear rating of the Flash memory.
I believe it is calculated something like this:
Wear Range Delta = [(MW - LW) / MRW] x 100
MW = P-E Cycles experienced by Most Worn block
LW = P-E Cycles experienced by Least Worn block
MRW = Max Rated Wear = P-E Cycle rating for the Flash memory
Your Delta is 58. If I assume a P/E rating of 5,000 the difference between least and most worn is significant and certainly well in excess of what the controller is designed to prevent.
58 = [(2,900) / 5,000] x 100
Or 3,000 P/E
58 = [(1,740) / 3,000] x 100
I suspect that static wear levelling can only occur when the drive is in idle mode. Most likely the controller cannot accept any other commands whilst it moves blocks around and flushes out any invalid data contained within the static data block.
Between post 2,060 & post 2,072 did your F3 have any power on idle time?
If static data cannot be rotated whilst the drive is active it means that the endurance app is inducing wear well above the rate that would occur if the data could be rotated.
Btw I believe that SF drives will issue a SMART trip once the reserve block count drops below the minimum allowable threshold.