‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

   On Thursday, July 1st, 2021 at 5:01 PM, Peter Fairbrother
   [1]peter@tsto.co.uk wrote:

   ... It seems simple to attack, 'oh look the

   file(system) has been changed, the user wrote or deleted a file'

     therefore he has accessed the filesystem.

   i did not write this, but i did want to point out: even reads drive
   obfuscating writes to the underlying volume.

   note that for SSDs in particular, this is a change in behavior: usually
   once error limit reached, and write leveling maxed out, you can still
   read what has been written.

   in this case, only reading can still drive duty cycle to failure on SSD
   type storage.

   i don't have a specific number on write overload for any activity
   (including reads) but this would be useful to know in advance...

   best regards,

References

   1. mailto:peter@tsto.co.uk