rsync failing on TUMBLEWEED on USB attached drive.

English Applications
1

I’ve had a situation for a few weeks when trying to back up my home directory on TUMBLEWEED.
This in entirely new behaviour of rsync. I’ve been using this method for years to back up my home directory to a USB attached drive.
It starts out normally then just stops. It’s claiming no space left on device when I finally hit CTRL-C because it’s obviously stopped. It has 575.4 GB free of 931.3 GB.

The command I’ve always used is

 rsync -av /home/flamebait /run/media/flamebait/BACKUP/flamebait/

This is the error I see when I do a CTRL-C

flamebait/.cache/google-chrome/Default/Cache/f_0b629a
^Crsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(636) [sender=3.1.2]
rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.15:46.png.u2GFyd" failed: Invalid argument (22)
rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.3:.jpg.12goj0" failed: Invalid argument (22)
rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.WTF?.jpg.uA71fA" failed: Invalid argument (22)
rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.flash.asp?id=84712.vzlotn" failed: Invalid argument (22)
rsync: rename "/run/media/flamebait/BACKUP/flamebait/flamebait/.cache/google-chrome/Default/Cache/.f_0988e9.6pWqiL" -> "flamebait/.cache/google-chrome/Default/Cache/f_0988e9": No space left on device (28)

How do I overcome this situation? This always used to work for backing up home. This is obviously new behaviour for me. I haven’t been able to back op my /home for weeks and I’m getting nervous about no recent backups.

2

We of course want to see the statement and it’s output that gave you that information (df -h or otherwise?)

3

I’m not clear of what you mean? I’ve pasted the output I see.
The rest were just a bunch of messages about being out of space.
It’s not giving me a lot of information. It just stopped behaving as it normally has for years.

4

We want to see the command that gave you the result of: “It has 575.4 GB free of 931.3 GB.”

5

After you see that error message:

  1. Is the external drive still mounted?
  2. Can you write to the external drive (say, using “touch” to create a tiny file?

There’s a possibility of a drive error causing the drive to be remounted as read-only, or even to have it seen on a different device name. You need to eliminate such possibilities before deciding that it is “rsync” rather than hardware. (The newer kernel might be fussier about the hardware).

6

This is what I am doing.
I plug the drive in and mount it with the device notifier in KDE Plasma
I open the drive using Dolphin.
I open a terminal in Dolphin from the tools drop down
I put my rsync command in on that terminal window.

I don’t know how to get the drive size and free space from the command line I don’t use the command line much. The information I have about the drive come from the properties you can get from right clicking on the folder.
His is a picture. of the information I took with spectacle. I cropped it so It’s just that popup.
https://drive.google.com/open?id=0B2eB_Izb5BMgWGQ0bGxMT05xTkU

7

It writes to the drive then just stop after a period of time without completing the rsync process.
Yes I can copy a file to and from the USB drive.
It’s as if some process that’s not part of rsync is stopping the rsync transfer and the error I’m am getting may be entirely wrong because that process that stops the transfer interferes with the rsync process.

8

Thank you. That is an explanation. We are very sceptical in believing information that just falls out of the blue. We always want to know why you say something. To say it bluntly, we do not believe people, we believe computers :wink:

BTW

df -h

will tel you those things not spoiled by any GUI interpretation.

9

That does not display on my system. Possibly because it is some Google site and I block most scripts. Please do not expect that all people trust Google.

This might be a better place: http://paste.opensuse.org/

10

/dev/sdb1 is the USB Drive

flamebait@flamebait:/run/media/flamebait/BACKUP> df -h
Filesystem               Size  Used Avail Use% Mounted on
devtmpfs                 5.9G     0  5.9G   0% /dev
tmpfs                    5.9G   29M  5.9G   1% /dev/shm
tmpfs                    5.9G  2.5M  5.9G   1% /run
tmpfs                    5.9G     0  5.9G   0% /sys/fs/cgroup
/dev/sda2                 20G  9.0G   10G  48% /
/dev/sda3                436G  163G  251G  40% /home
192.168.1.9:/nfs          50M  6.2M   44M  13% /nfs
192.168.1.9:/nfs/Movies  3.6T  2.5T  1.2T  70% /nfs/Movies
tmpfs                    1.2G   28K  1.2G   1% /run/user/1000
/dev/sdb1                932G  356G  576G  39% /run/media/flamebait/BACKUP
11

Perfect!. It is not that it must be with a CLI command. Your GUI screen copy is of course also right (when it would be vissible to non Google lovers ;)). Even you telling what you did to find that out makes what you say trustworthy. But copy/paste from the CLI is of course always the easiest thing to tell people here the message. Not much comment needed then.

12

As you can see I’m not out of space.
The rsync command that always has worked for years across several USB drives I’ve used for backup is not working.

Something in TUMBLEWEED recently changed to make it not work.
You can see two of my NFS mount points /nsf/Picture and /nsf/Music unmounted by some process too. That’s why they didn’t show up with this command. /nfs/Movies would be unmounted by this process too but it’s open in Dolphin. /nfs/ never gets unmounted by this process whatever it is that’s creeped into TUMBLEWEED. That’s a “new” thing as of several weeks.

How can I back up my /home? Now rsync no longer works?

13

That link took me to a google login page. I declined to login.

Okay, I copied the link, then used it in a different browser where I am logged in to google. I could see it there. As hcvv says, google drive is not a good place for sharing images.

14

Yes… I don’t have anywhere else to host it though :frowning:
The CLI command was used and the output is in the thread. :smiley:

15

Any interesting information if run dmesg in terminal?
With my system, using uas on USB3 I got some errors there

[Sep16 23:07] sd 8:0:0:0: [sdb] uas_eh_abort_handler ffff88042e5fd500 tag 0, inflight: CMD  +3.002595] scsi host8: uas_eh_task_mgmt: ABORT TASK timed out
  +0.000065] sd 8:0:0:0: uas_eh_device_reset_handler
  +0.000008] scsi host8: uas_eh_task_mgmt: LOGICAL UNIT RESET: error already running a task
  +0.000006] scsi host8: uas_eh_bus_reset_handler start
  +0.000055] usb 4-3.1.1: stat urb: killed, stream 2
  +0.000053] sd 8:0:0:0: [sdb] uas_zap_dead ffff88042e5fd500 tag 0, inflight: CMD abort
  +0.000004] sd 8:0:0:0: [sdb] abort completed
  +0.063188] usb 4-3.1.1: reset SuperSpeed USB device number 4 using xhci_hcd
  +0.011111] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880435de9c00
  +0.000012] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880435de9c48
  +0.000004] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880435de9c90
  +0.000004] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880435de9cd8
16

I don’t know what dmesg is.
Here is the output from what I googled that seemed to apply.
It’s a wall of text.


[158402.027410] **usb** 9-2: new SuperSpeed **USB** device number 3 using xhci_hcd
[158402.042878] **usb** 9-2: New **USB** device found, idVendor=0bc2, idProduct=a003
[158402.042882] **usb** 9-2: New **USB** device strings: Mfr=1, Product=2, SerialNumber=3
[158402.042885] **usb** 9-2: Product: Backup+ BK
[158402.042887] **usb** 9-2: Manufacturer: Seagate  
[158402.042889] **usb** 9-2: SerialNumber: NA5CR1K0
[158402.044885] **usb** 9-2: **USB** controller 0000:30:00.0 does not support streams, which are required by the UAS driver.
[158402.044888] **usb** 9-2: Please try an other **USB** controller if you wish to use UAS.
[158402.044891] **usb**-storage 9-2:1.0: **USB** Mass Storage device detected
[158402.045010] **usb**-storage 9-2:1.0: Quirks match for vid 0bc2 pid a003: 2000000
[158402.045029] scsi host11: **usb**-storage 9-2:1.0
[161972.920061] **usb** 3-1: **USB** disconnect, device number 46
[161973.148045] **usb** 3-2: **USB** disconnect, device number 47
[162186.416014] **usb** 3-1: new low-speed **USB** device number 48 using uhci_hcd
[162186.593683] **usb** 3-1: New **USB** device found, idVendor=046d, idProduct=c326
[162186.593688] **usb** 3-1: New **USB** device strings: Mfr=1, Product=2, SerialNumber=0

Tjis is what I get when AI have to do a CTRL-C because rsync stalls out.



     flamebait/.cache/google-chrome/Default/Cache/f_0b629a
^Crsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(636) [sender=3.1.2]
rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.xsession-errors-:0.The3ev" failed: Invalid argument (22)
rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.15:46.png.PT1erw" failed: Invalid argument (22)
rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.3:.jpg.cxzUTM" failed: Invalid argument (22)
rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.WTF?.jpg.zpXt8L" failed: Invalid argument (22)
rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.flash.asp?id=84712.eectme" failed: Invalid argument (22)
rsync: rename "/run/media/flamebait/BACKUP/flamebait/flamebait/.cache/google-chrome/Default/Cache/.f_0988e9.LpcGQQ" -> "flamebait/.cache/google-chrome/Default/Cache/f_0988e9": No space left on device (28)
rsync: rename "/run/media/flamebait/BACKUP/flamebait/flamebait/.cache/google-chrome/Default/Cache/.f_0a1f24.f3ol5Y" -> "flamebait/.cache/google-chrome/Default/Cache/f_0a1f24": No space left on device (28)
rsync: rename "/run/media/flamebait/BACKUP/flamebait/flamebait/.cache/google-chrome/Default/Cache/.f_0a1f27.vuker7" -> "flamebait/.cache/google-chrome/Default/Cache/f_0a1f27": No space left on device (28)
rsync: rename "/run/media/flamebait/BACKUP/flamebait/flamebait/.cache/google-chrome/Default/Cache/.f_0a1f29.zAUrUf" -> "flamebait/.cache/google-chrome/Default/Cache/f_0a1f29": No space left on device (28)



[156728.143401] **usb** 9-2: new SuperSpeed **USB** device number 2 using xhci_hcd
[156728.158871] **usb** 9-2: New **USB** device found, idVendor=0bc2, idProduct=a003
[156728.158875] **usb** 9-2: New **USB** device strings: Mfr=1, Product=2, SerialNumber=3
[156728.158877] **usb** 9-2: Product: Backup+ BK
[156728.158880] **usb** 9-2: Manufacturer: Seagate  
[156728.158882] **usb** 9-2: SerialNumber: NA5CR1K0
[156728.160184] **usb** 9-2: **USB** controller 0000:30:00.0 does not support streams, which are required by the UAS driver.
[156728.160187] **usb** 9-2: Please try an other **USB** controller if you wish to use UAS.
[156728.160190] **usb**-storage 9-2:1.0: **USB** Mass Storage device detected
[156728.161377] **usb**-storage 9-2:1.0: Quirks match for vid 0bc2 pid a003: 2000000
[156728.161398] scsi host10: **usb**-storage 9-2:1.0
[158284.744071] **usb** 9-2: **USB** disconnect, device number 2
[158402.027410] **usb** 9-2: new SuperSpeed **USB** device number 3 using xhci_hcd
[158402.042878] **usb** 9-2: New **USB** device found, idVendor=0bc2, idProduct=a003
[158402.042882] **usb** 9-2: New **USB** device strings: Mfr=1, Product=2, SerialNumber=3
[158402.042885] **usb** 9-2: Product: Backup+ BK
[158402.042887] **usb** 9-2: Manufacturer: Seagate  
[158402.042889] **usb** 9-2: SerialNumber: NA5CR1K0
[158402.044885] **usb** 9-2: **USB** controller 0000:30:00.0 does not support streams, which are required by the UAS driver.
[158402.044888] **usb** 9-2: Please try an other **USB** controller if you wish to use UAS.
[158402.044891] **usb**-storage 9-2:1.0: **USB** Mass Storage device detected
[158402.045010] **usb**-storage 9-2:1.0: Quirks match for vid 0bc2 pid a003: 2000000
[158402.045029] scsi host11: **usb**-storage 9-2:1.0
[161972.920061] **usb** 3-1: **USB** disconnect, device number 46
[161973.148045] **usb** 3-2: **USB** disconnect, device number 47
[162186.416014] **usb** 3-1: new low-speed **USB** device number 48 using uhci_hcd
[162186.593683] **usb** 3-1: New **USB** device found, idVendor=046d, idProduct=c326
[162186.593688] **usb** 3-1: New **USB** device strings: Mfr=1, Product=2, SerialNumber=0

All I know is it worked before and doesn’t now.
I really need to back up my /home.

17

I just think I found my problem.
That Seagate drive is failing.

I just took a HGST TOURO Mobile USB 3 hard drive out of its blister pack and set it up to use as a back up drive.
It’s having no problems and not stalling out.
I should have known better than to trust a Seagate :expressionless:

I think I found the source of my problem :frowning:


rsync -av /home/flamebait /run/media/flamebait/'TOURO Mobile'/Flamebait/

Seems to work just fine

18

That what I was concerned about in my first comment in this thread.

You have hardware issues. I’ve seen the same with one of my external drives. I filed bug 891168 about it.

It turned out to be a cabling problem.

All I know is it worked before and doesn’t now.
I really need to back up my /home.

The newer kernels or newer “udev” seem to be more sensitive to intermittent errors.

19

Congratulations you found it.