06-04-2009
Even after random data has been written to the drive it maybe possible to recover data using special tools that government agencies have access to.
If this is a problem for you and you really think that the government is out to get you, then you should simply destroy the drive and buy a new one.
Exactly how you destroy it is up to you but I read that the US government has a system for destroying computer equipment by cross cut, crush, grind, burn and then spread on the roads as grit in winter.
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I had an issue with a second hard disk in my machine. I have a sparc station running solaris 7. It was working fine but now it wont mount on boot up and when you try to mount it manually it gives an I/O error. I tried a different disk as a control which was fine. What I want to know is if my... (3 Replies)
Discussion started by: Henrik
3 Replies
2. UNIX for Dummies Questions & Answers
Hello all..
Iam New to Unix Environment. I need to copy .cpio file from CD to a Folder on Sun 5.8 Box.
Can anyone give me the commands to execute this ?..
Thanks in advance
Ron (4 Replies)
Discussion started by: vr76413
4 Replies
3. UNIX Desktop Questions & Answers
I have a cuestion. How Can I to add other hard disk to my computer? I need to configurate anyone? (4 Replies)
Discussion started by: hmaraver
4 Replies
4. UNIX for Dummies Questions & Answers
:eek: I use this Solaris to run CMS a call acounting software package for my job. No one could run reports today because it said the this when you logged on
"The following file systems are low, and could adversely affect server performance:
File system /: 99%full"
Can some one please explain... (9 Replies)
Discussion started by: mannyisme
9 Replies
5. SCO
hi
I've a fresh installation of SCO 5.0.7 on the IDE hard disk.
For SCSI hard disk I can declare, for example blc disk driver using:
# mkdev hd 0 SCSI-0 0 blc 0but it works for IDE hard disk? (3 Replies)
Discussion started by: ccc
3 Replies
6. Solaris
Hi freinds,
What is the command to find out the hard disk details (logical name, FS type etc,). Because i connected one ntfs partition and i don't know the hard disk logical and physical name to mount it.Kindly do the needful.
Thanks | P.Bharathiraja. :mad: (2 Replies)
Discussion started by: bharathiraja
2 Replies
7. Red Hat
When we write a programme,we declare variables and compiler allocates memory to them.I want to get access to the physical block number of hard-disk where actually the data is stored by the programme "
Some one help me out... (1 Reply)
Discussion started by: nagraz007
1 Replies
8. UNIX for Advanced & Expert Users
When we write a programme,we declare variables and compiler allocates memory to them.I want to get access to the physical block number of hard-disk where actually the data is stored by the programme "
Some one help me out... (3 Replies)
Discussion started by: nagraz007
3 Replies
9. Linux
Hi all,
I'm kind of new to programming in Linux & c/c++. I'm currently writing a FileManager using Ubuntu Linux(10.10) for Learning Purposes. I've got started on this project by creating a loopback device to be used as my virtual hard disk. After creating the loop back hard disk and mounting it... (23 Replies)
Discussion started by: shen747
23 Replies
10. BSD
hi
Has anyone already tried to migrate a hard disk with FreeBSD using recoverdisk? (1 Reply)
Discussion started by: ccc
1 Replies
SYNC(8) System Manager's Manual SYNC(8)
NAME
sync - synchronize data on disk with memory
SYNOPSYS
sync [--help] [--version]
DESCRIPTION
sync writes any data buffered in memory out to disk. This can include (but is not limited to) modified superblocks, modified inodes, and
delayed reads and writes. This must be implemented by the kernel; The sync program does nothing but exercise the sync(2) system call.
The kernel keeps data in memory to avoid doing (relatively slow) disk reads and writes. This improves performance, but if the computer
crashes, data may be lost or the filesystem corrupted as a result. sync ensures that everything in memory is written to disk.
sync should be called before the processor is halted in an unusual manner (e.g., before causing a kernel panic when debugging new kernel
code). In general, the processor should be halted using the shutdown(8) or reboot(8) or halt(8) commands, which will attempt to put the
system in a quiescent state before calling sync(2). (Various implementations of these commands exist; consult your documentation; on some
systems one should not call reboot(8) and halt(8) directly.)
GNU STANDARD OPTIONS
--help Print a usage message on standard output and exit successfully.
--version
Print version information on standard output, then exit successfully.
-- Terminate option list.
ENVIRONMENT
The variables LANG, LC_ALL, LC_CTYPE, and LC_MESSAGES have the usual meaning.
CONFORMING TO
POSIX 1003.2
NOTES
On Linux, sync is only guaranteed to schedule the dirty blocks for writing; it can actually take a short time before all the blocks are
finally written. The reboot(8) and halt(8) commands take this into account by sleeping for a few seconds after calling sync(2).
This page describes sync as found in the fileutils-4.0 package; other versions may differ slightly. Mail corrections and additions to
aeb@cwi.nl. Report bugs in the program to fileutils-bugs@gnu.ai.mit.edu.
SEE ALSO
sync(2), halt(8), reboot(8), update(8)
GNU fileutils 4.0 1998-11 SYNC(8)