Re: Copy with verify per block
- From: Arno Wagner <me@xxxxxxxxxxx>
- Date: 22 Nov 2007 15:22:30 GMT
Previously ByPass <bash@xxxxxxxxxx> wrote:
Just so this message bypasses Arnies killfile and make him curl-up and die.
I find it fascinating that you consider me important enough
to go to all this trouble just to get a simple message to me.
May I suggest that ignoring me would probably be more healthy
for you?
Arno
Eric Gisin wrote in news:13k6l18hs28uea6@xxxxxxxxxxxxxxxxxx.
"Alvin Andries" wrote in message news:47433030$0$12706$bf4948fe@xxxxxxxxxxxxxxxx
"Arno Wagner" me@xxxxxxxxxxx> wrote in message news:5qcqoqFv7cmfU1@xxxxxxxxxxxxxxxxxxxxxArnie is a certified moron.
Why don't you write your own copy program that
1) copies 1MB of data
2) flushes the I/O
3) reads the 1MB from the destination file and compares it
4) repeats until all data is copied?
This will still read from cache.
In Windows, use FILE_FLAG_NO_BUFFERING to bypass the OS cache.
However, the disk can still read from the cache (several MB now),
and only SCSI has an option to bypass the cache on reads. Does SATA2?
Can't you flush the cache like "sync" under UNIX? I think I recall a command
to do this for removable storage.
Safe Removal, or SysInternal's sync.
- References:
- Copy with verify per block
- From: Richard Foersom
- Re: Copy with verify per block
- From: Alvin Andries
- Re: Copy with verify per block
- From: Arno Wagner
- Re: Copy with verify per block
- From: Alvin Andries
- Re: Copy with verify per block
- From: Eric Gisin
- Re: Copy with verify per block
- From: ByPass
- Copy with verify per block
- Prev by Date: Re: Copy with verify per block
- Next by Date: Re: In-place file recovery?
- Previous by thread: Re: Copy with verify per block
- Next by thread: Re: Copy with verify per block
- Index(es):
Relevant Pages
|