rsync - Oct 2015 - [Bug 11578] New: Rsync does start with an error directly connecting an USB drive to a port

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
            Status: NEW
          Severity: normal
          Priority: P5
         Component: core
          Assignee: wayned at samba.org
          Reporter: armin_mohring at web.de
        QA Contact: rsync-qa at samba.org

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

https://bugzilla.samba.org/show_bug.cgi?id=11578

Armin Mohring <armin_mohring at web.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P5                          |P3

--- Comment #1 from Armin Mohring <armin_mohring at web.de> ---
error output:
rsync error: error in file io (code 11) at main.c (656) [Receiver=3.1.1]

This error occurs, when I connect an USB drive [USB HDD, 2TB) to an USB 3.0
port and try to start an incremental file transfer.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

https://bugzilla.samba.org/show_bug.cgi?id=11578

--- Comment #2 from Kevin Korb <rsync at sanitarium.net> ---
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.

https://bugzilla.samba.org/show_bug.cgi?id=11578

--- Comment #3 from Armin Mohring <armin_mohring at web.de> ---
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 using xhci_hcd
[ 5777.841134] usb 4-3: New USB device found, idVendor=0bc2, idProduct=3320
[ 5777.841139] usb 4-3: New USB device strings: Mfr=2, Product=3,
SerialNumber=1
[ 5777.841142] usb 4-3: Product: Expansion Desk
[ 5777.841144] usb 4-3: Manufacturer: Seagate
[ 5777.841146] usb 4-3: SerialNumber: NA4MVF15
[ 5777.843264] scsi8 : uas
[ 5777.843690] scsi 8:0:0:0: Direct-Access     Seagate  Expansion Desk   0712
PQ: 0 ANSI: 6
[ 5777.844184] sd 8:0:0:0: Attached scsi generic sg8 type 0
[ 5777.844251] sd 8:0:0:0: [sdh] Spinning up disk...
[ 5778.843059] .......ready
[ 5784.839976] sd 8:0:0:0: [sdh] 488378645 4096-byte logical blocks: (2.00
TB/1.81 TiB)
[ 5784.857762] sd 8:0:0:0: [sdh] Write Protect is off
[ 5784.857767] sd 8:0:0:0: [sdh] Mode Sense: 4f 00 00 00
[ 5784.857935] sd 8:0:0:0: [sdh] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[ 5784.858486] sd 8:0:0:0: [sdh] 488378645 4096-byte logical blocks: (2.00
TB/1.81 TiB)
[ 5784.881361]  sdh: sdh1
[ 5784.881816] sd 8:0:0:0: [sdh] 488378645 4096-byte logical blocks: (2.00
TB/1.81 TiB)
[ 5784.882346] sd 8:0:0:0: [sdh] Attached SCSI disk

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

https://bugzilla.samba.org/show_bug.cgi?id=11578

--- Comment #4 from Kevin Korb <rsync at sanitarium.net> ---
There are no device, block, or filesystem errors after that?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

https://bugzilla.samba.org/show_bug.cgi?id=11578

--- Comment #5 from Armin Mohring <armin_mohring at web.de> ---
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.

https://bugzilla.samba.org/show_bug.cgi?id=11578

Armin Mohring <armin_mohring at web.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

https://bugzilla.samba.org/show_bug.cgi?id=11578

Armin Mohring <armin_mohring at web.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |minor
         Resolution|INVALID                     |---
           Priority|P3                          |P2
             Status|RESOLVED                    |REOPENED

--- Comment #6 from Armin Mohring <armin_mohring at web.de> ---
Rsync does not detect, if a drive is not mounted.

In my case: I have an external USB3.0 drive with 2TB.
If the drive is not mounted, the following error occurs:

rsync error: error in file io (code 11) at main.c (656) [Receiver=3.1.1]

Improvemnt suggestion:

Rsync should detect, if the drive is mounted or not.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

https://bugzilla.samba.org/show_bug.cgi?id=11578

--- Comment #7 from Kevin Korb <rsync at sanitarium.net> ---
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 filesystem then you want a wrapper script.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

https://bugzilla.samba.org/show_bug.cgi?id=11578

--- Comment #8 from Armin Mohring <armin_mohring at web.de> ---
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 because:
You are the QA Contact for the bug.

https://bugzilla.samba.org/show_bug.cgi?id=11578

--- Comment #9 from Kevin Korb <rsync at sanitarium.net> ---
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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

https://bugzilla.samba.org/show_bug.cgi?id=11578

Armin Mohring <armin_mohring at web.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|REOPENED                    |RESOLVED

-- 
You are receiving this mail because:
You are the QA Contact for the bug.