Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I think you OK, with shred and/or just dd /dev/null on to this files.

Are you worry some one will take the plates out of drive to a forensic lab to try and restore your data, where do you draw the line ?

I guess you will have this problem on SSD's where the controller will write the new data on a new block (wear levelling), and the old data will still be on the memory chips (but not mapped)

I think you OK, with shred and/or just dd /dev/null on to this files.

Are you worry some one will take the plates out of drive to a forensic lab to try and restore your data, where do you draw the line ?

I guess you will have this problem on SSD's where the controller will write the new data on a new block (wear levelling), and the old data will still be on the memory chips (but not mapped)

Another option you have is to create a tmp file to fill all free space on the drive, and then use dd or shred, so there won't be other places for the drive to relocate the content.

I think you OK, with shred and/or just dd /dev/null on to this files.

Are you worry some one will take the plates out of drive to a forensic lab to try and restore your data, where do you draw the line ?

I guess you will have this problem on SSD's where the controller will write the new data on a new block (wear levelling), and the old data will still be on the memory chips (but not mapped)

Another option you have is to create a tmp file to fill all free space on the drive, and then use dd or shred, so there won't be other places for the drive to relocate the content.

[1] https://lwn.net/Articles/462437/

I think you OK, with shred and/or just dd /dev/null on to this files.

Are you worry some one will take the plates out of drive to a forensic lab to try and restore your data, where do you draw the line ?

I guess you will have this problem on SSD's where the controller will write the new data on a new block (wear levelling), and the old data will still be on the memory chips (but not mapped)

Another option you have is to create a tmp file to fill all free space on the drive, and then use dd or shred, so there won't be other places for the drive to relocate the content.

[1] https://lwn.net/Articles/462437/https://lwn.net/Articles/462437/ [2] https://stackoverflow.com/questions/30154094/data-destroy-using-shred-agains-ext4-filesystem

I think you OK, with shred and/or just dd /dev/null on to this files.

Are you worry some one will take the plates out of drive to a forensic lab to try and restore your data, where do you draw the line ?

I guess you will have this problem on SSD's where the controller will write the new data on a new block (wear levelling), and the old data will still be on the memory chips (but not mapped)

Another option you have is to create a tmp file to fill all free space on the drive, and then use dd or shred, so there won't be other places for the drive to relocate the content.

[1] https://lwn.net/Articles/462437/ [2]

  1. https://lwn.net/Articles/462437/
  2. https://stackoverflow.com/questions/30154094/data-destroy-using-shred-agains-ext4-filesystem