Robin is right.
Read back verification has lost its meaning since old days when we used
extremely unreliable media or transports. Who writes to floppies anymore? In
those old days you could/should use any copy program with a -v verify flag. But
read-back wore down your floppy faster, so in
That's not the same as a read-back write verification.
I believe that in general, rsync assumes that the disk actually
wrote whatever it was told to write.
However, a second pass with --checksum will, in fact, read the
entirety of both files; if a --checksum run doesn't actually
transfer
Hi,
you can use the switch --fsync to verify the transfer. From the manpage:
--fsync
Cause the receiving side to fsync each finished file.
This may slow down the transfer, but can help to
provide peace of mind when updating critical files.
--
Please use reply-all
directly after transferring your files will
verify that the files are written correctly (if the source hasn't
changed in the meantime). That might help to give some peace of mind.
Paul
On 7/12/22 02:31, Mark Filipak via rsync wrote:
Hello. Does rsync verify its writes?
Re, 'info rsync'.
Maybe
files are written correctly (if the source hasn't
changed in the meantime). That might help to give some peace of mind.
Paul
> On 7/12/22 02:31, Mark Filipak via rsync wrote:
> > Hello. Does rsync verify its writes?
> >
> > Re, 'info rsync'.
> >
> > Maybe I ju
Rsync does not verify writes. --checksum doesn't verify anything.
Sounds like you want a file verification tool. The simplest would be
md5sum.
On 7/12/22 02:31, Mark Filipak via rsync wrote:
Hello. Does rsync verify its writes?
Re, 'info rsync'.
Maybe I just being stupid, but there's
Hello. Does rsync verify its writes?
Re, 'info rsync'.
Maybe I just being stupid, but there's no mention of verification in the 'DESCRIPTION' section, so
despite the words in the 'OPTIONS' section, '-c, --checksum' topic (which I may be misinterpreting),
I assume rsync does not verify except
