backing up crashing after upgrade to pve 9

F

FiskerK

New Member
May 29, 2024
2
0
1
Good day

my daily backup task has started crashing after upgrading from pve8 to pve9
I backup my 4 vms to my truenas vm, that has worked for years now, but after the upgrade my truenas vm will crash during the file transfer and the backpu proces will become stuck forcing me to hard reset the machine.

my log of the latest backup run test:
Code: 
Oct 21 09:53:17 pve kernel: netfs: FS-Cache loaded
Oct 21 09:53:17 pve kernel: NFS: Registering the id_resolver key type
Oct 21 09:53:17 pve kernel: Key type id_resolver registered
Oct 21 09:53:17 pve kernel: Key type id_legacy registered
Oct 21 09:53:17 pve nfsrahead[3232]: setting /mnt/pve/Truenas readahead to 128
Oct 21 09:53:21 pve pvesh[1980]: Starting VM 106
Oct 21 09:53:21 pve pve-guests[1981]: <root@pam> starting task UPID:pve:00000CA5:00004510:68F73BF1:qmstart:106:root@pam:
Oct 21 09:53:21 pve pve-guests[3237]: start VM 106: UPID:pve:00000CA5:00004510:68F73BF1:qmstart:106:root@pam:
Oct 21 09:53:21 pve systemd[1]: Started 106.scope.
Oct 21 09:53:22 pve kernel: tap106i0: entered promiscuous mode
Oct 21 09:53:22 pve kernel: vmbr0: port 3(fwpr106p0) entered blocking state
Oct 21 09:53:22 pve kernel: vmbr0: port 3(fwpr106p0) entered disabled state
Oct 21 09:53:22 pve kernel: fwpr106p0: entered allmulticast mode
Oct 21 09:53:22 pve kernel: fwpr106p0: entered promiscuous mode
Oct 21 09:53:22 pve kernel: vmbr0: port 3(fwpr106p0) entered blocking state
Oct 21 09:53:22 pve kernel: vmbr0: port 3(fwpr106p0) entered forwarding state
Oct 21 09:53:22 pve kernel: fwbr106i0: port 1(fwln106i0) entered blocking state
Oct 21 09:53:22 pve kernel: fwbr106i0: port 1(fwln106i0) entered disabled state
Oct 21 09:53:22 pve kernel: fwln106i0: entered allmulticast mode
Oct 21 09:53:22 pve kernel: fwln106i0: entered promiscuous mode
Oct 21 09:53:22 pve kernel: fwbr106i0: port 1(fwln106i0) entered blocking state
Oct 21 09:53:22 pve kernel: fwbr106i0: port 1(fwln106i0) entered forwarding state
Oct 21 09:53:22 pve kernel: fwbr106i0: port 2(tap106i0) entered blocking state
Oct 21 09:53:22 pve kernel: fwbr106i0: port 2(tap106i0) entered disabled state
Oct 21 09:53:22 pve kernel: tap106i0: entered allmulticast mode
Oct 21 09:53:22 pve kernel: fwbr106i0: port 2(tap106i0) entered blocking state
Oct 21 09:53:22 pve kernel: fwbr106i0: port 2(tap106i0) entered forwarding state
Oct 21 09:53:22 pve pve-guests[3237]: VM 106 started with PID 3252.
Oct 21 09:53:25 pve pvesh[1980]: Starting CT 110
Oct 21 09:53:25 pve pve-guests[1981]: <root@pam> starting task UPID:pve:00000D04:000046A1:68F73BF5:vzstart:110:root@pam:
Oct 21 09:53:25 pve pve-guests[3332]: starting CT 110: UPID:pve:00000D04:000046A1:68F73BF5:vzstart:110:root@pam:
Oct 21 09:53:25 pve systemd[1]: Created slice system-pve\x2dcontainer.slice - PVE LXC Container Slice.
Oct 21 09:53:25 pve systemd[1]: Started pve-container@110.service - PVE LXC Container: 110.
Oct 21 09:53:26 pve kernel: kauditd_printk_skb: 115 callbacks suppressed
Oct 21 09:53:26 pve kernel: audit: type=1400 audit(1761033206.339:127): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-110_</var/lib/lxc>" pid=3390 comm="apparmor_parser"
Oct 21 09:53:26 pve kernel: vmbr0: port 4(veth110i0) entered blocking state
Oct 21 09:53:26 pve kernel: vmbr0: port 4(veth110i0) entered disabled state
Oct 21 09:53:26 pve kernel: veth110i0: entered allmulticast mode
Oct 21 09:53:26 pve kernel: veth110i0: entered promiscuous mode
Oct 21 09:53:27 pve kernel: eth0: renamed from veth7E705f
Oct 21 09:53:27 pve pvestatd[1931]: modified cpu set for lxc/110: 0
Oct 21 09:53:27 pve pvesh[1980]: Starting CT 111
Oct 21 09:53:27 pve pve-guests[1981]: <root@pam> starting task UPID:pve:00000DD3:0000476A:68F73BF7:vzstart:111:root@pam:
Oct 21 09:53:27 pve pve-guests[3539]: starting CT 111: UPID:pve:00000DD3:0000476A:68F73BF7:vzstart:111:root@pam:
Oct 21 09:53:27 pve systemd[1]: Started pve-container@111.service - PVE LXC Container: 111.
Oct 21 09:53:27 pve kernel: vmbr0: port 4(veth110i0) entered blocking state
Oct 21 09:53:27 pve kernel: vmbr0: port 4(veth110i0) entered forwarding state
Oct 21 09:53:28 pve kernel: audit: type=1400 audit(1761033208.306:128): apparmor="STATUS" operation="profile_load" profile="/usr/bin/lxc-start" name="lxc-111_</var/lib/lxc>" pid=3635 comm="apparmor_parser"
Oct 21 09:53:28 pve kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
Oct 21 09:53:28 pve kernel: Loaded X.509 cert 'benh@debian.org: 577e021cb980e0e820821ba7b54b4961b8b4fadf'
Oct 21 09:53:28 pve kernel: Loaded X.509 cert 'romain.perier@gmail.com: 3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
Oct 21 09:53:28 pve kernel: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Oct 21 09:53:28 pve kernel: Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
Oct 21 09:53:28 pve kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Oct 21 09:53:28 pve kernel: cfg80211: failed to load regulatory.db
Oct 21 09:53:28 pve kernel: vmbr0: port 5(veth111i0) entered blocking state
Oct 21 09:53:28 pve kernel: vmbr0: port 5(veth111i0) entered disabled state
Oct 21 09:53:28 pve kernel: veth111i0: entered allmulticast mode
Oct 21 09:53:28 pve kernel: veth111i0: entered promiscuous mode
Oct 21 09:53:28 pve kernel: eth0: renamed from vethUNsS5y
Oct 21 09:53:29 pve kernel: vmbr0: port 5(veth111i0) entered blocking state
Oct 21 09:53:29 pve kernel: vmbr0: port 5(veth111i0) entered forwarding state
Oct 21 09:53:29 pve pve-guests[1980]: <root@pam> end task UPID:pve:000007BD:00001174:68F73B6D:startall::root@pam: OK
Oct 21 09:53:29 pve systemd[1]: Finished pve-guests.service - PVE guests.
Oct 21 09:53:29 pve systemd[1]: Starting pvescheduler.service - Proxmox VE scheduler...
Oct 21 09:53:30 pve pvescheduler[4102]: starting server
Oct 21 09:53:30 pve systemd[1]: Started pvescheduler.service - Proxmox VE scheduler.
Oct 21 09:53:30 pve systemd[1]: Reached target multi-user.target - Multi-User System.
Oct 21 09:53:30 pve systemd[1]: Reached target graphical.target - Graphical Interface.
Oct 21 09:53:30 pve systemd[1]: Startup finished in 22.570s (firmware) + 4.220s (loader) + 35.943s (kernel) + 2min 29.890s (userspace) = 3min 32.625s.
Oct 21 09:53:52 pve tailscaled[1558]: wgengine: Reconfig: [Tw4c2] changed from "discokey:a70d7daf34cb081ba7952e3f4e268e20cd536a059e676ff3517c39afc60fb006" to "discokey:fab9a75b76fb262473635a2d376a0923e6f5bbfea5bf5026102f7878045d7402"
Oct 21 09:54:54 pve pvedaemon[1954]: <root@pam> starting task UPID:pve:000012EF:0000692E:68F73C4E:vzdump::root@pam:
Oct 21 09:54:54 pve pvedaemon[4847]: INFO: starting new backup job: vzdump 107 105 106 104 --notes-template '{{guestname}}' --prune-backups 'keep-daily=6,keep-last=3,keep-monthly=11,keep-weekly=3,keep-yearly=3' --mailnotification failure --all 0 --node pve --compress zstd --storage Truenas --notification-mode notification-system --fleecing 0 --mode snapshot
Oct 21 09:54:54 pve pvedaemon[4847]: INFO: Starting Backup of VM 104 (qemu)
Oct 21 09:55:38 pve pvedaemon[4847]: INFO: Finished Backup of VM 104 (00:00:44)
Oct 21 09:55:38 pve pvedaemon[4847]: INFO: Starting Backup of VM 105 (qemu)
Oct 21 09:59:10 pve pvestatd[1931]: storage 'Truenas' is not online
Oct 21 09:59:10 pve pvestatd[1931]: status update time (13.348 seconds)
Oct 21 09:59:23 pve pvestatd[1931]: storage 'Truenas' is not online
Oct 21 09:59:23 pve pvestatd[1931]: status update time (13.375 seconds)
Oct 21 09:59:42 pve pvestatd[1931]: storage 'Truenas' is not online
Oct 21 09:59:42 pve pvestatd[1931]: status update time (19.365 seconds)
Oct 21 09:59:58 pve pvestatd[1931]: storage 'Truenas' is not online
Oct 21 09:59:58 pve pvestatd[1931]: status update time (15.566 seconds)
Oct 21 10:00:13 pve pvestatd[1931]: storage 'Truenas' is not online
Oct 21 10:00:14 pve pvestatd[1931]: status update time (15.570 seconds)
Oct 21 10:00:29 pve pvestatd[1931]: storage 'Truenas' is not online
Oct 21 10:00:29 pve pvestatd[1931]: status update time (15.543 seconds)
Oct 21 10:00:45 pve pvestatd[1931]: storage 'Truenas' is not online
Oct 21 10:00:45 pve pvestatd[1931]: status update time (15.556 seconds)
Oct 21 10:01:00 pve pvestatd[1931]: storage 'Truenas' is not online
Oct 21 10:01:00 pve pvestatd[1931]: status update time (15.498 seconds)
Oct 21 10:01:25 pve pvestatd[1931]: storage 'Truenas' is not online
Oct 21 10:01:25 pve pvestatd[1931]: status update time (24.448 seconds)
Oct 21 10:01:40 pve pvestatd[1931]: storage 'Truenas' is not online
Oct 21 10:01:40 pve pvestatd[1931]: status update time (15.341 seconds)
Oct 21 10:01:55 pve pvestatd[1931]: storage 'Truenas' is not online
Oct 21 10:01:55 pve pvestatd[1931]: status update time (15.347 seconds)
Oct 21 10:01:58 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:01:58 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:01:58 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:01:58 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:01 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:01 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:04 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:04 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:08 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:08 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:11 pve pvestatd[1931]: storage 'Truenas' is not online
Oct 21 10:02:11 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:11 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:11 pve pvestatd[1931]: status update time (15.367 seconds)
Oct 21 10:02:14 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:14 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:17 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:17 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:20 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:20 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:23 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:23 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:26 pve pvestatd[1931]: storage 'Truenas' is not online
Oct 21 10:02:26 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:26 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:26 pve pvestatd[1931]: status update time (15.360 seconds)
Oct 21 10:02:29 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:29 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:32 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:32 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:35 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:35 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:38 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:41 pve pvestatd[1931]: storage 'Truenas' is not online
Oct 21 10:02:41 pve kernel: nfs: server 192.168.100.220 not responding, still trying
Oct 21 10:02:41 pve pvestatd[1931]: status update time (15.372 seconds)
Oct 21 10:02:43 pve kernel: INFO: task ksmtuned:1376 blocked for more than 122 seconds.
Oct 21 10:02:43 pve kernel:       Tainted: P           O       6.14.11-4-pve #1
Oct 21 10:02:43 pve kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 21 10:02:43 pve kernel: task:ksmtuned        state:D stack:0     pid:1376  tgid:1376  ppid:1      task_flags:0x400040 flags:0x00000002
Oct 21 10:02:43 pve kernel: Call Trace:
Oct 21 10:02:43 pve kernel:  <TASK>
Oct 21 10:02:43 pve kernel:  __schedule+0x466/0x1400
Oct 21 10:02:43 pve kernel:  ? setattr_copy+0x1aa/0x230
Oct 21 10:02:43 pve kernel:  schedule+0x29/0x130
Oct 21 10:02:43 pve kernel:  schedule_preempt_disabled+0x15/0x30
Oct 21 10:02:43 pve kernel:  __mutex_lock.constprop.0+0x44d/0x7a0
Oct 21 10:02:43 pve kernel:  ? _kstrtoull+0x39/0xa0
Oct 21 10:02:43 pve kernel:  __mutex_lock_slowpath+0x13/0x20
Oct 21 10:02:43 pve kernel:  mutex_lock+0x3b/0x50
Oct 21 10:02:43 pve kernel:  run_store+0x62/0x3f0
Oct 21 10:02:43 pve kernel:  ? _copy_from_iter+0xf1/0x610
Oct 21 10:02:43 pve kernel:  ? __kmalloc_noprof+0x24f/0x510
Oct 21 10:02:43 pve kernel:  kobj_attr_store+0xf/0x40
Oct 21 10:02:43 pve kernel:  sysfs_kf_write+0x3b/0x60
Oct 21 10:02:43 pve kernel:  kernfs_fop_write_iter+0x149/0x1f0
Oct 21 10:02:43 pve kernel:  vfs_write+0x299/0x460
Oct 21 10:02:43 pve kernel:  ksys_write+0x70/0xf0
Oct 21 10:02:43 pve kernel:  __x64_sys_write+0x19/0x30
Oct 21 10:02:43 pve kernel:  x64_sys_call+0x2a3/0x2310
Oct 21 10:02:43 pve kernel:  do_syscall_64+0x7e/0x170
Oct 21 10:02:43 pve kernel:  ? filp_flush+0x5a/0xb0
Oct 21 10:02:43 pve kernel:  ? arch_exit_to_user_mode_prepare.isra.0+0x22/0x120
Oct 21 10:02:43 pve kernel:  ? syscall_exit_to_user_mode+0x38/0x1d0
Oct 21 10:02:43 pve kernel:  ? do_syscall_64+0x8a/0x170
Oct 21 10:02:43 pve kernel:  ? ksys_dup3+0x9d/0x120
Oct 21 10:02:43 pve kernel:  ? arch_exit_to_user_mode_prepare.isra.0+0x22/0x120
Oct 21 10:02:43 pve kernel:  ? syscall_exit_to_user_mode+0x38/0x1d0
Oct 21 10:02:43 pve kernel:  ? do_syscall_64+0x8a/0x170
Oct 21 10:02:43 pve kernel:  ? arch_exit_to_user_mode_prepare.isra.0+0x22/0x120
Oct 21 10:02:43 pve kernel:  ? syscall_exit_to_user_mode+0x38/0x1d0
Oct 21 10:02:43 pve kernel:  ? do_syscall_64+0x8a/0x170
Oct 21 10:02:43 pve kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Oct 21 10:02:43 pve kernel: RIP: 0033:0x79bcc659a687
Oct 21 10:02:43 pve kernel: RSP: 002b:00007ffda6b641d0 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Oct 21 10:02:43 pve kernel: RAX: ffffffffffffffda RBX: 000079bcc6508740 RCX: 000079bcc659a687
Oct 21 10:02:43 pve kernel: RDX: 0000000000000002 RSI: 0000580520c4ad00 RDI: 0000000000000001
Oct 21 10:02:43 pve kernel: RBP: 0000580520c4ad00 R08: 0000000000000000 R09: 0000000000000000
Oct 21 10:02:43 pve kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000002
Oct 21 10:02:43 pve kernel: R13: 000079bcc66f35c0 R14: 000079bcc66f0e80 R15: 0000000000000000
Oct 21 10:02:43 pve kernel:  </TASK>

i can only conlcude something has changed after the upgrade, since it only crashes during backup its hard for me to see what is going wrong, so i hope someone else might be able to see someting.
I ran out of caracters I can add the specific backup log if its of interest.
 
news said:
"storage 'Truenas' is not online" is written, so check the ips on both side and your right!
Click to expand...
I guess I can describe the situation better:

before the backup process starts, everything is online and I can access truenas without issues. then the backup starts and the first vm completes then somewhere between 30-60% through the next vm truenas and maybe also the rest of the vms becomes unresponsive.

Here is the backup log:
Code: 
Header
Proxmox
Virtual Environment 9.0.11
Virtual Machine 107 (TruenasScale) on node 'pve'
No Tags
Logs
()
INFO: starting new backup job: vzdump 107 105 106 104 --notes-template '{{guestname}}' --prune-backups 'keep-daily=6,keep-last=3,keep-monthly=11,keep-weekly=3,keep-yearly=3' --mailnotification failure --all 0 --node pve --compress zstd --storage Truenas --notification-mode notification-system --fleecing 0 --mode snapshot
INFO: Starting Backup of VM 104 (qemu)
INFO: Backup started at 2025-10-21 09:54:54
INFO: status = running
INFO: VM Name: haos
INFO: include disk 'scsi0' 'local-zfs:vm-104-disk-1' 32G
INFO: include disk 'efidisk0' 'local-zfs:vm-104-disk-0' 4M
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating vzdump archive '/mnt/pve/Truenas/dump/vzdump-qemu-104-2025_10_21-09_54_54.vma.zst'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task '97b4700c-002a-40da-b354-f3f2e7e74ccc'
INFO: resuming VM again
INFO:   2% (801.1 MiB of 32.0 GiB) in 3s, read: 267.0 MiB/s, write: 179.3 MiB/s
INFO:   5% (1.8 GiB of 32.0 GiB) in 6s, read: 358.9 MiB/s, write: 175.8 MiB/s
INFO:  13% (4.2 GiB of 32.0 GiB) in 9s, read: 806.0 MiB/s, write: 165.3 MiB/s
INFO:  17% (5.6 GiB of 32.0 GiB) in 12s, read: 482.1 MiB/s, write: 197.4 MiB/s
INFO:  23% (7.6 GiB of 32.0 GiB) in 15s, read: 667.0 MiB/s, write: 175.9 MiB/s
INFO:  30% (9.8 GiB of 32.0 GiB) in 18s, read: 760.0 MiB/s, write: 167.5 MiB/s
INFO:  41% (13.1 GiB of 32.0 GiB) in 21s, read: 1.1 GiB/s, write: 128.1 MiB/s
INFO:  55% (17.9 GiB of 32.0 GiB) in 24s, read: 1.6 GiB/s, write: 113.8 MiB/s
INFO:  69% (22.1 GiB of 32.0 GiB) in 27s, read: 1.4 GiB/s, write: 102.6 MiB/s
INFO:  83% (26.7 GiB of 32.0 GiB) in 30s, read: 1.5 GiB/s, write: 63.6 MiB/s
INFO:  91% (29.4 GiB of 32.0 GiB) in 33s, read: 934.0 MiB/s, write: 143.3 MiB/s
INFO:  95% (30.6 GiB of 32.0 GiB) in 36s, read: 404.8 MiB/s, write: 211.2 MiB/s
INFO: 100% (32.0 GiB of 32.0 GiB) in 38s, read: 711.4 MiB/s, write: 121.0 MiB/s
INFO: backup is sparse: 26.42 GiB (82%) total zero data
INFO: transferred 32.00 GiB in 38 seconds (862.3 MiB/s)
INFO: archive file size: 2.33GB
INFO: adding notes to backup
INFO: prune older backups with retention: keep-daily=6, keep-last=3, keep-monthly=11, keep-weekly=3, keep-yearly=3
INFO: removing backup 'Truenas:backup/vzdump-qemu-104-2025_10_14-03_00_04.vma.zst'
INFO: pruned 1 backup(s) not covered by keep-retention policy
INFO: Finished Backup of VM 104 (00:00:44)
INFO: Backup finished at 2025-10-21 09:55:38
INFO: Starting Backup of VM 105 (qemu)
INFO: Backup started at 2025-10-21 09:55:38
INFO: status = running
INFO: VM Name: CloudBox
INFO: include disk 'scsi0' 'local-zfs:vm-105-disk-1' 82G
INFO: include disk 'efidisk0' 'local-zfs:vm-105-disk-0' 1M
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating vzdump archive '/mnt/pve/Truenas/dump/vzdump-qemu-105-2025_10_21-09_55_38.vma.zst'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task '1300e3a1-6874-4382-a72b-b21468e93028'
INFO: resuming VM again
INFO:   1% (1.2 GiB of 82.0 GiB) in 3s, read: 401.2 MiB/s, write: 241.3 MiB/s
INFO:   2% (1.8 GiB of 82.0 GiB) in 6s, read: 222.3 MiB/s, write: 218.7 MiB/s
INFO:   3% (2.6 GiB of 82.0 GiB) in 10s, read: 205.7 MiB/s, write: 193.5 MiB/s
INFO:   4% (3.4 GiB of 82.0 GiB) in 14s, read: 206.6 MiB/s, write: 206.4 MiB/s
INFO:   5% (4.2 GiB of 82.0 GiB) in 18s, read: 203.0 MiB/s, write: 197.9 MiB/s
INFO:   6% (4.9 GiB of 82.0 GiB) in 22s, read: 178.5 MiB/s, write: 173.5 MiB/s
INFO:   7% (5.8 GiB of 82.0 GiB) in 28s, read: 143.2 MiB/s, write: 142.9 MiB/s
INFO:   8% (6.7 GiB of 82.0 GiB) in 33s, read: 184.9 MiB/s, write: 179.3 MiB/s
INFO:   9% (7.4 GiB of 82.0 GiB) in 37s, read: 196.7 MiB/s, write: 196.0 MiB/s
INFO:  10% (8.3 GiB of 82.0 GiB) in 42s, read: 168.2 MiB/s, write: 167.9 MiB/s
INFO:  11% (9.1 GiB of 82.0 GiB) in 47s, read: 170.4 MiB/s, write: 162.6 MiB/s
INFO:  12% (9.9 GiB of 82.0 GiB) in 51s, read: 198.5 MiB/s, write: 198.3 MiB/s
INFO:  13% (10.7 GiB of 82.0 GiB) in 56s, read: 179.1 MiB/s, write: 172.7 MiB/s
INFO:  14% (11.6 GiB of 82.0 GiB) in 1m 1s, read: 166.0 MiB/s, write: 165.1 MiB/s
INFO:  15% (12.3 GiB of 82.0 GiB) in 1m 6s, read: 160.2 MiB/s, write: 159.7 MiB/s
INFO:  16% (13.2 GiB of 82.0 GiB) in 1m 11s, read: 187.0 MiB/s, write: 180.9 MiB/s
INFO:  17% (14.0 GiB of 82.0 GiB) in 1m 15s, read: 192.1 MiB/s, write: 191.7 MiB/s
INFO:  18% (14.8 GiB of 82.0 GiB) in 1m 19s, read: 202.1 MiB/s, write: 198.7 MiB/s
INFO:  19% (15.7 GiB of 82.0 GiB) in 1m 24s, read: 188.5 MiB/s, write: 188.1 MiB/s
INFO:  20% (16.5 GiB of 82.0 GiB) in 1m 29s, read: 157.3 MiB/s, write: 155.8 MiB/s
INFO:  21% (17.3 GiB of 82.0 GiB) in 1m 34s, read: 162.4 MiB/s, write: 161.3 MiB/s
INFO:  22% (18.2 GiB of 82.0 GiB) in 1m 40s, read: 153.5 MiB/s, write: 152.1 MiB/s
INFO:  23% (18.9 GiB of 82.0 GiB) in 1m 44s, read: 185.8 MiB/s, write: 184.0 MiB/s
INFO:  24% (19.8 GiB of 82.0 GiB) in 1m 49s, read: 190.7 MiB/s, write: 186.9 MiB/s
INFO:  25% (20.6 GiB of 82.0 GiB) in 1m 54s, read: 161.7 MiB/s, write: 161.5 MiB/s
INFO:  26% (21.3 GiB of 82.0 GiB) in 1m 58s, read: 188.5 MiB/s, write: 188.3 MiB/s
INFO:  27% (22.3 GiB of 82.0 GiB) in 2m 4s, read: 165.5 MiB/s, write: 165.3 MiB/s
INFO:  28% (23.0 GiB of 82.0 GiB) in 2m 8s, read: 185.8 MiB/s, write: 185.5 MiB/s
INFO:  29% (23.8 GiB of 82.0 GiB) in 2m 12s, read: 188.5 MiB/s, write: 188.0 MiB/s
INFO:  30% (24.9 GiB of 82.0 GiB) in 2m 21s, read: 122.4 MiB/s, write: 121.9 MiB/s
INFO:  31% (25.5 GiB of 82.0 GiB) in 2m 24s, read: 216.3 MiB/s, write: 216.3 MiB/s
INFO:  32% (26.3 GiB of 82.0 GiB) in 2m 30s, read: 140.2 MiB/s, write: 139.7 MiB/s
INFO:  33% (27.2 GiB of 82.0 GiB) in 2m 36s, read: 148.0 MiB/s, write: 147.8 MiB/s
INFO:  34% (27.9 GiB of 82.0 GiB) in 2m 41s, read: 144.3 MiB/s, write: 144.1 MiB/s
INFO:  35% (28.7 GiB of 82.0 GiB) in 2m 46s, read: 171.8 MiB/s, write: 168.0 MiB/s
INFO:  36% (29.6 GiB of 82.0 GiB) in 2m 52s, read: 144.4 MiB/s, write: 144.1 MiB/s
INFO:  37% (30.5 GiB of 82.0 GiB) in 3m 2s, read: 94.2 MiB/s, write: 93.8 MiB/s
INFO:  38% (31.3 GiB of 82.0 GiB) in 3m 6s, read: 205.7 MiB/s, write: 199.8 MiB/s
INFO:  39% (32.1 GiB of 82.0 GiB) in 3m 9s, read: 261.0 MiB/s, write: 258.8 MiB/s

So something happens in the middle of the process but was fine last week.
 
You must log in or register to reply here.
Top Bottom