https://bugzilla.samba.org/show_bug.cgi?id=11578
--- Comment #5 from Armin Mohring ---
I think I have found the error:
the usb 3.0 Hdd must be mounted first and then it can be acessed.
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for mos
https://bugzilla.samba.org/show_bug.cgi?id=11578
--- Comment #4 from Kevin Korb ---
There are no device, block, or filesystem errors after that?
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for most replies to avoid omitting the mailing l
https://bugzilla.samba.org/show_bug.cgi?id=11578
--- Comment #3 from Armin Mohring ---
This is the relevant part from dmesg after connecting the drive to an USB 3.0
port:
5773.601144] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 5777.829686] usb 4-3: new SuperSpeed USB device number 6 usin
https://bugzilla.samba.org/show_bug.cgi?id=11578
--- Comment #2 from Kevin Korb ---
There should be additional errors. If not from rsync then from dmesg.
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for most replies to avoid omitting the
https://bugzilla.samba.org/show_bug.cgi?id=11578
Armin Mohring changed:
What|Removed |Added
Priority|P5 |P3
--- Comment #1 from Armin Mohring ---
https://bugzilla.samba.org/show_bug.cgi?id=11578
Bug ID: 11578
Summary: Rsync does start with an error directly connecting an
USB drive to a port
Product: rsync
Version: 3.1.1
Hardware: x64
OS: Linux
Ok, thank you for this extra info. I have experienced exactly what you
described. The rsync dry run is _still_ running after being started at
1:30am PST :)
But it is finding the right files to update. Most of the entries are:
>fc
Which is what I want.
So, just because I see:
>f
at the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
if you see >f it is doing something to the file. At least a
delta-xfer. If it was just a metadata change it would show cf. If
you see an >fc without a t then that is an example where rsync found a
file that didn't match even though the timestamps di
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --checksum generally takes a lot longer than --size-only. A delta
transfer generally goes quicker than a checksum. However, if you want
to make a list of what is corrupt a checksumming utility that is less
stupid than rsync can be useful. I say th
