https://bugzilla.samba.org/show_bug.cgi?id=11578
Armin Mohring changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugzilla.samba.org/show_bug.cgi?id=11578
Armin Mohring changed:
What|Removed |Added
Severity|normal |minor
https://bugzilla.samba.org/show_bug.cgi?id=11578
--- Comment #7 from Kevin Korb ---
Rsync has no idea (or way) to know that you are trying to rsync to a separate
disk. You give it a source and a target and it uses what is there. If you
need to check for a mounted
https://bugzilla.samba.org/show_bug.cgi?id=11578
--- Comment #9 from Kevin Korb ---
You have no idea how many people would complain if rsync didn't create a
non-existing target directory. It is already a very common complaint that
rsync won't create more than one deep.
--
https://bugzilla.samba.org/show_bug.cgi?id=11578
--- Comment #8 from Armin Mohring ---
Why should rsync that know.
There is an error, if the specified folder does not exist.
Could be an external disk or partition or something else.
--
You are receiving this mail
https://bugzilla.samba.org/show_bug.cgi?id=11578
Armin Mohring changed:
What|Removed |Added
Resolution|--- |INVALID
https://bugzilla.samba.org/show_bug.cgi?id=11578
Armin Mohring changed:
What|Removed |Added
Priority|P5 |P3
--- Comment #1
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
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
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
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.
--
11 matches
Mail list logo