"... how would I go about "shredding"
that file?" [emphasis added]
May I review some disk-data fundamentals? A file on disk may be updated in one of two (and a half) ways:
- in-place (same location). This is possible only when the file contents (or a portion thereof) are being replaced. This typically is the method used for a data-base, where data in a record are being changed. Only the cluster involved is re/over-written. This is a "record rewrite" operation. (In principle, a database may be enormous, and a total file rewrite is both unnecessary and time-consuming.)
- (1/2 way). If a file is being expanded - either a database record size is being lengthened, or a new record is being added to the file (any type of file) - the file, or portions thereof, will be written to a new location. This is a "file append" operation. New clusters are allocated somewhere else on the disk. The file management system ensures that there is linkage between the old sections and the new ones.
- new location. This must be used for a file copy, and the most common method if a file is small. The internal process details are interesting but somewhat boring. The result is that the file is moved to new cluster(s) on the disk, the old location is indexed as free space.
- Note: a file Delete does nothing to the space occupied by that file. It only removes the directory entry to that file, and reassigns the clusters to the free pool.
The Defrag operation 'squeezes out' the free space and 're-contiguizes' all the clusters that relate to each file. This is where performance is improved, since all the sectors for a file are adjacent - no disk-dance is needed.
So? "Shredding a file" would require that not only the 'present' file location be scrambled, but that all the old locations likewise be located and erased (assuming that the sectors have not been reused). How many old locations are there, and where are they?
A Defrag before your Format will help, since it will rewrite some low-address clusters. But multiple over-writes of the unused sectors - overwrites with varying bit patterns - are necessary to thoroughly randomize the magnetic domains.
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0