https://devzone.nordicsemi.com/f/nordic-q-a/109032/fds-and-additional-wear-levelingBased on the Nordic documentation , I see that there&#39;s already wear leveling built into FDS, which is one of the benefits of using it over something like fstorage . From what I have seen so far, it appears that there&#39;s no way to limit the size of aen-USTelligent Community 13Fri, 08 Mar 2024 13:58:51 GMThttps://devzone.nordicsemi.com/thread/472970?ContentTypeID=1Fri, 08 Mar 2024 13:58:51 GMT137ad170-7792-4731-bb38-c0d22fbe4515:1720579e-ff3b-48d8-bc3e-2dc635066d50tesc<p>Hi,</p> <p>What you suggest should be doable, yes, using the FDS API. Please note however that there are no concepts of &quot;maximum number of records of a given type&quot; in FDS, so you would have to implement that mechanism yourself. Please also consider first if this scheme is really what you want. It sounded like you wanted to discard new log messages, if the log was already full. Logs are typically most useful if they contain the last log messages, as typically you would want to read the logs if some problem has occured or some recent events need investigating.</p> <p>Regarding flash wear and planning for the device to last, the most important parameters are the amount of data written (during the expected lifetime of the device) and the number of pages used for FDS.</p> <p>Please note, that a record update in FDS is actually a write and a delete; The new version of the record is written, and the old version of the record is marked for deletion (invalidated.) Thus an update appending data to an existing record spends more writes than storing that appended data as its own record.</p> <p>Regards,<br />Terje</p><div style="clear:both;"></div>