shred() not working on ext* file systems


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users shred() not working on ext* file systems
# 1  
Old 07-15-2009
shred() not working on ext* file systems

When vfat format my128kb flash drive, shred works fine. But, when I format it using ext2 or ext3, shred() exits with this error:

Code:
shred: /dev/sdb1: pass 1/1 (random)...
shred: /dev/sdb1: error writing at offset 12288: Invalid argument

Anyone know what is going on?
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

ext File

I have a log file that I want to extract the field name and the field value and write them to a text file for importation it a database table for reporting purposes. How can I extract the desired data from this file . Example: dbt_dbid=4 dbt_dbid is the field name 4 is the field value... (4 Replies)
Discussion started by: JolietJake
4 Replies

2. Shell Programming and Scripting

Script to monitor for new file with ext .err and size > 0 bytes and perform a action or command

Hi All, I need to create a script to monitor a dir for new files with ext .err and also it should b a non empty files. and perform a action or command . We have a new ETL application that runs on a linux server, every times a etl fails it creates a .err file or updates the existing .err... (4 Replies)
Discussion started by: MAKHAN
4 Replies

3. Shell Programming and Scripting

Duplicate name diff file ext

Hi All I have converted a load of files to different formats but I am now left with a folder with loads of differnt files All of them are called the same, the only differnce is the file extension (Sizes also vary so cannot do anything with MD5) example file1.abc file1.xyz file2.abc... (2 Replies)
Discussion started by: tofa83
2 Replies

4. UNIX for Advanced & Expert Users

shred multiple options

I've created a wxpython gui for the shred command. I can successfully mix and match all the shred options except two: -size and --random-source. (Man page definitions below). -size and --random-source seem to only work when they are used as the sole option passed. For example, I can zero a... (0 Replies)
Discussion started by: codecellar
0 Replies

5. UNIX for Advanced & Expert Users

Working with remote Unix files systems from Windows

I am currently using Samba to access remote Unix file systems from Windows. However, it is slow, and I presume insecure in the sense that file contents are transmitted unencrypted. I also wonder if passwords are transmitted in plain text in this protocol or not. For these reasons I am looking for... (2 Replies)
Discussion started by: Bilge
2 Replies

6. UNIX for Dummies Questions & Answers

Shred utility

Hi experts. We have a HP-Unix server, we deleted some files and folders from the server. Is there any utilities that we can use to ensure those deleted files and folders are not recoverable? We used rm command to delete these files. Cheers, RT:confused: (1 Reply)
Discussion started by: robtseng
1 Replies

7. Shell Programming and Scripting

rename file to file.ext.datetime

Hi, I need to rename a file like this to include date and time: Original File : error.log Date time: Sep 20, 2007 14:10:10 New File Name: error.log.20070920_1410 How can I get date and time stame and include it in mv command. Thanks in advance (2 Replies)
Discussion started by: tripsat
2 Replies

8. UNIX for Dummies Questions & Answers

Help using shred instead of rm

Hi, I have this script which runs pretty well bar a couple of problems, I am trying to emulate the rm command and this means I can't use rm directory, I inted to alias my script to rm and then use mv to move files to a trash folder rather than delete forever. The problem: when I use mv to... (18 Replies)
Discussion started by: jack1981
18 Replies
Login or Register to Ask a Question
SHRED(1)								FSF								  SHRED(1)

NAME
shred - delete a file securely, first overwriting it to hide its contents SYNOPSIS
shred [OPTIONS] FILE [...] DESCRIPTION
Overwrite the specified FILE(s) repeatedly, in order to make it harder for even very expensive hardware probing to recover the data. Mandatory arguments to long options are mandatory for short options too. -f, --force change permissions to allow writing if necessary -n, --iterations=N Overwrite N times instead of the default (25) -s, --size=N shred this many bytes (suffixes like K, M, G accepted) -u, --remove truncate and remove file after overwriting -v, --verbose show progress -x, --exact do not round file sizes up to the next full block -z, --zero add a final overwrite with zeros to hide shredding - shred standard output --help display this help and exit --version output version information and exit Delete FILE(s) if --remove (-u) is specified. The default is not to remove the files because it is common to operate on device files like /dev/hda, and those files usually should not be removed. When operating on regular files, most people use the --remove option. CAUTION: Note that shred relies on a very important assumption: that the filesystem overwrites data in place. This is the traditional way to do things, but many modern filesystem designs do not satisfy this assumption. The following are examples of filesystems on which shred is not effective: * log-structured or journaled filesystems, such as those supplied with AIX and Solaris (and JFS, ReiserFS, XFS, Ext3, etc.) * filesystems that write redundant data and carry on even if some writes fail, such as RAID-based filesystems * filesystems that make snapshots, such as Network Appliance's NFS server * filesystems that cache in temporary locations, such as NFS version 3 clients * compressed filesystems In addition, file system backups and remote mirrors may contain copies of the file that cannot be removed, and that will allow a shredded file to be recovered later. AUTHOR
Written by Colin Plumb. REPORTING BUGS
Report bugs to <bug-coreutils@gnu.org>. COPYRIGHT
Copyright (C) 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU- LAR PURPOSE. SEE ALSO
The full documentation for shred is maintained as a Texinfo manual. If the info and shred programs are properly installed at your site, the command info shred should give you access to the complete manual. shred (coreutils) 4.5.3 February 2003 SHRED(1)