shred entire device or partition , remove file system first?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If shredding an entire device or partition does the file system being used make a difference.
Doesn't shred overwrite data in place?
shred writes random data several times. If you are shredding a partition or whole disk, it doesn't care what filesystem you used, because it will be turned into random, meaningless data. There won't even be a "filesystem" (of any sort) when shred has finished. So the filesystem doesn't matter.
The filesystem certainly does make a difference. See the shred man pages for discussion on which filesystems are least/most affected by shredding.
CAUTION: Note that shred relies on a very important assumption: that the file system overwrites
data in place. This is the traditional way to do things, but many modern file system designs do
not satisfy this assumption. The following are examples of file systems on which shred is not
effective, or is not guaranteed to be effective in all file system modes:
* log-structured or journaled file systems, such as those supplied with AIX and Solaris (and JFS,
ReiserFS, XFS, Ext3, etc.)
* file systems that write redundant data and carry on even if some writes fail, such as RAID-based
* file systems that make snapshots, such as Network Appliance's NFS server
* file systems that cache in temporary locations, such as NFS version 3 clients
* compressed file systems
Last edited by bigrigdriver; 05-26-2008 at 11:41 AM.
Yep. My bad. But you could probably do the job a lot faster my simply using cfdisk /dev/sda (or whatever the device is) to delete the partition(s). Then Write the change to delete the partition table. You would have a very hard time finding any files on the disk then.
If you are extremely paranoid about anyone using very expensive, high powered equipment to recover files, then nothing works better than sulphuric acid.
But you could probably do the job a lot faster my simply using cfdisk /dev/sda (or whatever the device is) to delete the partition(s). Then Write the change to delete the partition table. You would have a very hard time finding any files on the disk then.
Nope, writing the partition table back effectively restores it with all files intact. A tool like testdisk does restore the partition table with ease and is included on many LiveCD-s, e. g. Knoppix.
If you are extremely paranoid ...then nothing works better than sulphuric acid.
"Fire" is easier to get hold of nowadays
I confess that dead or redundant (who wants a 512MB HDD nowadays?) disks I take apart. Well, I'm a hardware man at heart, and the insides are often interesting.
By the time I have fingerprints all over the platters and have rescued a few good fridge magnets, I defy anyone to get the data back
@writedom: It looks as though you can just shred the partition / disk, if you'd like it to be re-usable but otherwise unrecoverable.