3.6 FAT12/16/32

Support: tffs-lib: not official - not written by the filesystem’s creators, written without any specifications.

Compiling requirements:

• tffs-lib, the Tiny FAT FS library. Go to
  https://github.com/likema/tffs-lib
  to get the library (former address: ’http://code.google.com/p/tffs-lib/’). To make WipeFreeSpace work faster, apply the patch that removes synchronising the filesystem from TFFS (WipeFreeSpace does its own synchronising):

  ‘patch -F10 -p0 < /path/to/wipefreespace-XX/patches/tffs-speed.diff’

  If you experience crashes (especially on 64-bit systems), you may try to apply these patches as well:

  ‘patch -F10 -p0 < /path/to/wipefreespace-XX/patches/tffs-free-fix.diff’

  ‘patch -F10 -p0 < /path/to/wipefreespace-XX/patches/tffs-overflow-fix.diff’

  ‘patch -F10 -p0 < /path/to/wipefreespace-XX/patches/tffs-fat-eof-fix.diff’

  ‘patch -F10 -p0 < /path/to/wipefreespace-XX/patches/tffs-dir-fix.diff’

  After applying any patch, you need to recompile and install the library - libtffs.a - and ALL its header - *.h - files (including the private ones, from the src directory).

Operations:

• wiping the free space
• wiping free space in partially used blocks (NOTE: may crash on sparse files and other exotic objects)
• wiping deleted files’ names (at least the short ones)
• wiping deleted files’ data (part of free space or partially used blocks)

NOTE: the original TFFS library does its own data flushing (in the ‘HAI_writesector()’ function), so even when WipeFreeSpace is told to perform just one wiping iteration (which uses the system/drive cache on other filesystems and doesn’t flush the data immediately), the data is flushed after each sector, which makes FAT12/16/32 wiping really slow.

NOTE: filesystems with object names of length 64 or more may cause problems with traversal and thus may not be fully wiped (if a file can’t be opened, its last block can’t be wiped, if a directory can’t be opened, objects inside it can’t be wiped).