Re: testing files for read errors by copying to /dev/null
On Mon, 24 Mar 2008 10:23:33 -0600, Charles Russell <NOSPAM@bellsouth.net> wrote:
>I would like to test the integrity of a CD (after burning from .iso) by
>reading all its files and looking for error messages. (I'm using Cygwin,
>so I cannot access the CD drive as a dev/, only as a mounted filesystem.)
>If I try
>cp -rv /cygdrive/d/* /dev/null
>then I get a message that /dev/null is not a file or directory
it is on a real unix or linux system.
>If I try
>tar -cvf /dev/null /cygdrive/d
>then the command runs so fast it cannot possibly be reading the whole CD.
it's probably reading cache.
>If I try
>find /cygdrive/d -type f -name '*' -print -exec cat {} >/dev/null \;
>then the disk drive seems active for a reasonable length of time, but
>despite the -print flag, I get no output to confirm what is actually
>happening. I expected the filename to be printed before each file was
>read.
>What is the best way to do what I am attempting?
md5sum
|