GNU bug report logs - #17149
shred - tape data

Previous Next

Package: coreutils;

Reported by: Rupert Russell <Rupert.Russell <at> ilmor.co.uk>

Date: Mon, 31 Mar 2014 15:45:04 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log


Message #20 received at 17149 <at> debbugs.gnu.org (full text, mbox):

From: Pádraig Brady <P <at> draigBrady.com>
To: Rupert Russell <Rupert.Russell <at> ilmor.co.uk>
Cc: "17149-done <at> debbugs.gnu.org" <17149 <at> debbugs.gnu.org>
Subject: Re: bug#17149: shred - tape data
Date: Tue, 01 Apr 2014 13:38:27 +0100
On 04/01/2014 01:18 PM, Rupert Russell wrote:
> Pádraig,
> 
> This seems to be getting my task done.
> 
> for i in $(seq 1 $NUMTAPES) ; do
> 		mtx -f $LOADER load $i
> 	for j in $(seq 1 $NUMWIPES); do 
> 			shred -v -n 1 $TAPE
>  			mt -f $TAPE rewind
> 	done         
>            		shred -v -z -n 0 $TAPE
> 		mt -f $TAPE rewind
> 		mtx -f $LOADER unload $i
> done
> 
> By the way, is there a difference between what these two write to the media?
> mt -f $TAPE erase   and
> shred -z -n 0 $TAPE

It depends I suppose.
`mt erase` might trigger a command to the hardware
to activate a degausser or something, rather than writing zeros,
though from a very quick google it defaults to writing zeros.

BTW I find this a handy way to see what shred is doing
rather than reading the docs:

  strace -e write shred -s 1K /dev/null

thanks,
Pádraig.




This bug report was last modified 11 years and 44 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.