Re: [Bug 1910588] Re: rsync backup hang

Hi Terry,

Thanks for the response.

I have sort of tried with -36. The rsync always hung when it was working
on a large file; an outlook.pst file for example. I have not run the
backup script since it did work using the 5.8.0-33 kernel.

However, I have since updated the kernel to 5.8.0-36. I use dd as a
crude measure of performance with large sequential files as follows...

$ dd if=Win10_20H2_v2_English_x64.iso of=/dev/null bs=8192k

The source file is a Windows 10 install .iso as the name would suggest,
and is about 6GB. The reported speed when the copy works is about 475
MB/s. If run again it gets 2GB/s from cache.

The dd command (and cp -p) hang is the same way (-36 kernel) as the
rsync did with -34 but the failures were intermittent.

I opened another bug report for the dd/cp hang with -36 kernel as well
but I suspect they're really the same problem.

I'll try the dd command with the .so file sourced from the boot ssd and
from the backup hard drive tomorrow. I reinstalled today from the 20.10
desktop image. The last failure seemed to result in boot drive corruption.

Yesterday while I was working on this response the machine hung again
but this time only Firefox and Thunderbird. New terminal windows opened
but were unresponsive. The mouse was responsive but not the keyboard.

It's starting to look more like a hardware problem but I haven't been
able to indentify the failing component yet. I'm going to reinstall on a
newer machine today; AMD Ryzen 3700X with M.2 ssd boot drive and 64GB
memory. It has a dated Radeon 260X GPU though and I'm not sure how good
the support is for it.

I'll get back to you later today when that's done.

Jack

On 2021-01-12 4:21 p.m., Terry Rudd wrote:
> Have you tested with 5.8.0-36?
>

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1910588

Title:
rsync backup hang

Status in linux package in Ubuntu:
Confirmed

Bug description:
I'm using rsync to backup directories. With kernel 5.8.0.34 it hangs
requiring machine reset; no response from mouse or keyboard. No
response to ping from a windows machine. All drive activity stops. The
hang occurs with the backup drive connected via sata and via usb3
(adapter)

The source directories are ext4 (boot drive ssd) and zfs (raidz1 four
x 4TB drives). The destination is a single 3TB drive formatted with
zfs (drive is about 20% full).

The hang occurred about 6 times before I decided to go back to kernel
5.8.0-33 (hangs ocurred with -34). The backup worked fine with kernel
-33 (sata and usb3 connect). The install is 20.10. Please let me know
if you need more information.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-34-generic 5.8.0-34.37
ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
Uname: Linux 5.8.0-34-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: jcw0624 5100 F.... pulseaudio
/dev/snd/pcmC0D0p: jcw0624 5100 F...m pulseaudio
/dev/snd/controlC1: jcw0624 5100 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 7 12:07:11 2021
InstallationDate: Installed on 2020-10-03 (96 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IwConfig:
lo no wireless extensions.

enp9s0 no wireless extensions.
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic root=UUID=89ed8b12-0ade-4a0f-91c3-8f9f4b3a8a81 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.8.0-34-generic N/A
linux-backports-modules-5.8.0-34-generic N/A
linux-firmware 1.190.2
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to groovy on 2020-11-09 (59 days ago)
dmi.bios.date: 10/16/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1604
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: SABERTOOTH 990FX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910588/+subscriptions