-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 15/01/14 14:00, Carl Hartung wrote:

On Wed, 15 Jan 2014 15:34:13 +0200 ellanios82 ellanios82 wrote:

...

Hello List,

- occasionally rsync causes oS 13.1 to freeze , necessitating turn off power to reboot.

- the rsync instruction, leading to freeze is :

................

rsync -avr --delete --delete-after --exclude=/ /home/ /mnt

.............................

Did anyone experience similar event?

'-a' = "archive mode" & is already recursive (your 'r' is redundant)

'--delete' and '--delete-after' are two forms of the same command. Use one, or the other, but not both.

'--exclude= needs single quotes around the items to exclude and you want to use multiple directives instead of combining them into one, e.g. (mind the line wrap!):

'rsync -av --delete-after --exclude='/' --exclude='/home/' \ --exclude='/mnt/' {source} {target}

Carl, I believe the OP intended '/home/' to be the {source} and '/mnt' to be the {target}, i.e. he wants to copy the contents of /home into /mnt.

Don't forget to explicitly include or exclude the trailing slash on {source} ... it is very important ... see 'man rsync'

hth & regards,

Carl

- -- Bob Williams System: Linux 3.11.6-4-desktop Distro: openSUSE 13.1 (x86_64) with KDE Development Platform: 4.12.0 Uptime: 12:00pm up 5 days 16:15, 5 users, load average: 0.99, 1.19, 1.14 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLWockACgkQ0Sr7eZJrmU4D7ACfV2LqXFbUulLwbvkrcIs7YM+9 kp8AoJNgUvzIrJNZHnmSX1H045rCAHj/ =84nC -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-01-15 18:36, ellanios82 wrote:

dmesg : my understanding is not sufficient to spot logged cause : there are 991 lines of dmesg !

The last lines when it hangs is what is interesting :-) However, if the machine locks... :-? Maybe you can keep "tailf /var/log/messages" on a terminal as you run the sync. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)

El 15/01/14 14:52, Carlos E. R. escribió:

Maybe you can keep "tailf /var/log/messages" on a terminal as you run the sync.

we want the output of journalctl -k -f (in a different terminal while running rsync) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

El 15/01/14 16:27, Carlos E. R. escribió:

On 2014-01-15 19:25, Cristian Rodríguez wrote:

...

journalctl -k -f

Warning: only in 13.1.

In 12.3 I get:

Telcontar:~ # journalctl -k -f

yeah, $SUBJECT says "oS 13.1" :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 01/15/2014 07:58 PM, Greg Freemyer wrote:

...

On 01/15/2014 05:00 PM, Cristian Rodríguez wrote:

...

El 15/01/14 10:34, ellanios82 escribió:

...

Hello List,

- occasionally rsync causes oS 13.1 to freeze , necessitating turn off power to reboot.

- the rsync instruction, leading to freeze is :

................

rsync -avr --delete --delete-after --exclude=/ /home/ /mnt

.............................

Did anyone experience similar event?

There may be many causes.. an IO flood is a likely cause, or a kernel bug.. what does "dmesg" says ?

---

thanks all : yes intent is to back-up /home to another disk mounted on /mnt

..............

dmesg : my understanding is not sufficient to spot logged cause : there are 991 lines of dmesg ! Is your destination USB2 or USB3? If USB3, is it both the device and

On Wed, Jan 15, 2014 at 12:36 PM, ellanios82 wrote: the port that are USB3?

I'm not positive about this, but based on using them it seems USB2 is a polled / non-interrupt driven technology and USB3 is interrupt drive. That means USB2 is extremely CPU intensive to use it and the rest of your PC suffers to a large extent.

USB3 seems far more usable and I don't see the massive overall PC degradation when it is in use. I assume therefore it is interrupt driven.

A quick google and review of docs implies USB2 is interrupt driven for slow devices like keyboards / mice (HID devices), but not for fast devices like disks.

Regardless, if you are currently using USB2 and you have a USB3 disk handy, I would try it and see if you see the same performance impact.

the device is : Model: "Intenso External USB 3.0" ........... thank you -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Thu, 16 Jan 2014, Linda Walsh wrote:

ellanios82 wrote:

...

On 01/15/2014 07:58 PM, Greg Freemyer wrote:

...

...

Is your destination USB2 or USB3? If USB3, is it both the device and the port that are USB3?

I'm not positive about this, but based on using them it seems USB2 is a polled / non-interrupt driven technology and USB3 is interrupt drive. That means USB2 is extremely CPU intensive to use it and the rest of your PC suffers to a large extent.

USB3 seems far more usable and I don't see the massive overall PC degradation when it is in use. I assume therefore it is interrupt driven.

A quick google and review of docs implies USB2 is interrupt driven for slow devices like keyboards / mice (HID devices), but not for fast devices like disks.

Regardless, if you are currently using USB2 and you have a USB3 disk handy, I would try it and see if you see the same performance impact.

---

the device is :

Model: "Intenso External USB 3.0"

---

How old is your computer? Do you know if it came with USB3.0 or USB2.0 ports?

(USB3 only in past 2-3 years at most).

If you really want to use your USB3 disk, from what Greg says, you might want to invest in a USB3 card for your computer -- then the USB3 disk can use the "efficient" USB3 port instead of an inefficient USB2 port.

Note, rsync has a "--bwlimit=RATE" [try 1M as a test value, if system is too slow, try 500K or lower, if system is fine and transfer is too slow try 2M and go higher...?].

to tell if your system has a USB 3.0 device, an easy to use tool looks like the usbview (usbview-2.0-2.1.3.x86_64)...

running it allows you to see what USB port your disk is mounted on and to see the speed of the USB "Host Controller"

Mine say 12Mb/s or 480Mb/s (USB1.1 or USB2.0) -- I don't have any USB3.0 devices, so can't tell you what they would say.

(if you need to install usbview, might try "zypper in usbview" as root.

I just tried usbview on my ASUS M5A97 EVO based system, it's xhci port was listed as speed unknown, so perhaps usbview is not up with USB-3. The standard command lsusb -t summarises speed: kosmos1:~ # lsusb -t /: Bus 11.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/4p, 12M /: Bus 10.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/2p, 12M /: Bus 09.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/5p, 12M /: Bus 08.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 07.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 5000M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/5p, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M In reality using the iotop command to monitor USB-3 IO shows around 100 MB/s to a Seagate 2TB external Expansion Drive when copying the openSUSE 13.3 DVD to an encrypted ext4 filesystem. USB-3 is stable on my system - I use it for rsync'ing backups once a week - as suggested, it may be worth investing in a card to get a speed up. But given ellanios82's system is currently unstable, it seems quite important to determine the cause before speeding anything on cards. I guess checking dmesg etc for errors is a good first step? Are there any BIOS settings to do with USB or overclocking enabled or set inappropriately? Does/did it work reliably with another OS? Has the media been checked for errors? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org