Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Data remanence
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Causes== {{unreferenced section|date=May 2025}} Many [[operating system]]s, [[file manager]]s, and other software provide a facility where a [[computer file|file]] is not immediately [[File deletion|deleted]] when the user requests that action. Instead, the file is moved to a [[Recycle bin (computing)|holding area]] (i.e. the "trash"), making it easy for the user to undo a mistake. Similarly, many software products automatically create backup copies of files that are being edited, to allow the user to restore the original version, or to recover from a possible crash (''[[autosave]]'' feature). Even when an explicit deleted file retention facility is not provided or when the user does not use it, operating systems do not actually remove the contents of a file when it is deleted unless they are aware that explicit erasure commands are required, like on a [[solid-state drive]]. (In such cases, the operating system will issue the [[Serial ATA]] [[Trim (computing)|TRIM]] command or the [[SCSI]] UNMAP command to let the drive know to no longer maintain the deleted data.) Instead, they simply remove the file's entry from the [[file system]] [[directory (file systems)|directory]] because this requires less work and is therefore faster, and the contents of the file—the actual data—remain on the [[data storage device|storage medium]]. The data will remain there until the [[operating system]] reuses the space for new data. In some systems, enough filesystem [[metadata]] are also left behind to enable easy [[undeletion]] by commonly available [[utility software]]. Even when undelete has become impossible, the data, until it has been overwritten, can be read by software that reads [[disk sector]]s directly. [[Computer forensics]] often employs such software. Likewise, [[Disk formatting|reformatting]], [[Disk partitioning|repartitioning]], or [[Disk image|reimaging]] a system is unlikely to write to every area of the disk, though all will cause the disk to appear empty or, in the case of reimaging, empty except for the files present in the image, to most software. Finally, even when the storage media is overwritten, physical properties of the media may permit recovery of the previous contents. In most cases however, this recovery is not possible by just reading from the storage device in the usual way, but requires using laboratory techniques such as disassembling the device and directly accessing/reading from its components.{{Citation needed|reason=If the "usual way" refers to reading via the filesystem driver, reading prior contents was never claimed possible. But also when using magnetic force microscopes to analyze magnetic hard drives, overwriting a sector once is sufficient to make the previous data irretrievable, according to this: https://kaleron.edu.pl/throwing-Gutmanns-algorithm-into-the-trash.php|date=January 2025}} {{em|{{slink||Complications}}}} below gives further explanations for causes of data remanence.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)