I recently had this problem on a long-running parallel rsync process backing up
to an external esata drive. That is, a ~2 hour process running parallel
instances of rsync like so:
cat ~/items.txt | parallel rsync --info=progress2 --append-verify --numeric-ids
-ah {} /esata_dir/
This was an Ubuntu 18.04.6 system, see attached picture (ignore the
ata18 lines). The process failed 3 times, and may have been the cause of
the untimely death of 2 internal hard drives in a RAID-10 config. It
kept throwing machine check exceptions, which lead me to this write-up
on a Google search: https://cloudlinux.zendesk.com/hc/en-
us/articles/360014017379-Kernel-panic-not-syncing.
I was never able to capture crash dumps or anything for debugging, but
that article gave me the idea of disabling c-states in the BIOS, and the
rsync process succeeded on the 4th attempt. The failure always occurred
after about 45-60 minutes into the rsync process. I might guess that
some c-state change during rsync caused some major problems
(power/current irregularities), causing the MCE errors and possibly
killing 2 of my drives. I ran memtest86+ on the system and it passed all
tests running it 2x through.
I have rasdaemon and mcelog set up to hopefully capture anything in the
future. I don't believe kdump (or 'linux-crashdump') will be helpful, as
I understand it requires a non-encrypted swap.
** Attachment added: "rsync_err_msg.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778932/+attachment/5645320/+files/rsync_err_msg.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1778932
Title:
rsync can trigger system crash
Status in linux package in Ubuntu:
Confirmed
Bug description:
I'm not sure how much of this is rsync or something else in my system.
I can reliably trigger this using rsync to transfer files from one
drive to another drive on my computer. the source is ssd and
destination is mdadm raid 1 partition. will attach syslog messages.
after it is triggered, the the system becomes unresponsive and
requires a hard reboot. running rysnc as user, no special privileges.
root@music:~# lsb_release -rd
Description: Ubuntu 18.04 LTS
Release: 18.04
apt-cache policy rsync
rsync:
Installed: 3.1.2-2.1ubuntu1
Candidate: 3.1.2-2.1ubuntu1
Version table:
*** 3.1.2-2.1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
uname -a
Linux music 4.15.0-23-lowlatency #25-Ubuntu SMP PREEMPT Wed May 23 20:39:43
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: rsync 3.1.2-2.1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-23.25-lowlatency 4.15.18
Uname: Linux 4.15.0-23-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jun 27 10:08:36 2018
InstallationDate: Installed on 2018-03-31 (87 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
TERM=xterm-256color
LANGUAGE=en_US
PATH=(custom, no user)
SourcePackage: rsync
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: papa 5200 F.... pulseaudio
/dev/snd/controlC0: papa 5200 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ca9d6033-d98d-4fba-be24-599f112ac941
InstallationDate: Installed on 2018-03-31 (89 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-lowlatency
root=/dev/mapper/xubuntu--vg-root ro splash fsck.mode=force fsck.repair=yes
vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-lowlatency 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-23-lowlatency N/A
linux-backports-modules-4.15.0-23-lowlatency N/A
linux-firmware 1.173.1
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: bionic
Uname: Linux 4.15.0-23-lowlatency x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: False
dmi.bios.date: 04/19/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4011
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B350-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778932/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
