On Oct 31, 2006 15:14 -0500, Nikolai Joukov wrote:
1. One of the patches performs N overwrites with configurable patterns
(can comply with NIST and NISPOM standards). Because of the transaction
compaction we had to separately add overwriting as separate transactions.
Fortunately, the whole
Andreas Dilger wrote:
On Oct 31, 2006 15:14 -0500, Nikolai Joukov wrote:
1. One of the patches performs N overwrites with configurable patterns
(can comply with NIST and NISPOM standards). Because of the transaction
compaction we had to separately add overwriting as separate
1. One of the patches performs N overwrites with configurable patterns
(can comply with NIST and NISPOM standards). Because of the transaction
compaction we had to separately add overwriting as separate transactions.
Fortunately, the whole procedure is still atomic due to the orphan list.
Sorry if this has been discussed already, I couldn't find anything in
the list archive about it. What about adding the possibility of
shredding or erasing free blocks on an ext4 filesystem?
I value my privacy and the privacy of the people I host, and I often
use shred(1) when erasing files from
On Tue, Oct 31, 2006 at 11:36:11AM +0100, Samuel Tardieu wrote:
I value my privacy and the privacy of the people I host, and I often
use shred(1) when erasing files from my server. The goal is to avoid
that either a hacker or a post-mortem analysis gets ancien data from
my disk. There are
