Shutdown PBS bringt Kernelfehler

CoolTux

CoolTux

Famous Member
Proxmox Subscriber
Mar 14, 2019
1,134
194
108
48
Hallo,

Mein PBS ist über PVE virtualisiert und ich lasse einmal in der Woche ein Backup Job mit STOP für den PBS auf dem PVE laufen. Leider wird der PBS nicht vernünftig runter gefahren. Er bleibt in einem inkosistenten Zustand stehen. Ich muss dann immer hart STOP machen über den PVE.
Auffällige Log Meldungen zu der Zeit des Job Startes sind vorallem


Code: 
Jan 31 12:15:06 p-pbs postfix/postfix-script[2221133]: stopping the Postfix mail system
Jan 31 12:15:06 p-pbs postfix/master[977]: terminating on signal 15
Jan 31 12:15:22 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:15:37 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:15:52 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:16:08 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:16:23 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:16:38 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:16:54 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:17:09 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:17:24 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:17:40 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:17:55 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:18:11 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:18:26 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:18:37 p-pbs kernel: INFO: task systemd:1 blocked for more than 122 seconds.
Jan 31 12:18:37 p-pbs kernel:       Tainted: P           O        6.17.4-2-pve #1
Jan 31 12:18:37 p-pbs kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 31 12:18:37 p-pbs kernel: task:systemd         state:D stack:0     pid:1     tgid:1     ppid:0      task_flags:0x400100 flags:0x00004002
Jan 31 12:18:37 p-pbs kernel: Call Trace:
Jan 31 12:18:37 p-pbs kernel:  <TASK>
Jan 31 12:18:37 p-pbs kernel:  __schedule+0x468/0x1310
Jan 31 12:18:37 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:18:37 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:18:37 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:18:37 p-pbs kernel:  ? add_wait_queue+0x76/0xa0
Jan 31 12:18:37 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:18:37 p-pbs kernel:  schedule+0x27/0xf0
Jan 31 12:18:37 p-pbs kernel:  schedule_preempt_disabled+0x15/0x30
Jan 31 12:18:37 p-pbs kernel:  __ww_mutex_lock.constprop.0+0x7fd/0xda0
Jan 31 12:18:37 p-pbs kernel:  __ww_mutex_lock_slowpath+0x16/0x30
Jan 31 12:18:37 p-pbs kernel:  ww_mutex_lock+0xec/0x100
Jan 31 12:18:37 p-pbs kernel:  drm_modeset_lock+0x5f/0xf0
Jan 31 12:18:37 p-pbs kernel:  drm_atomic_get_plane_state+0x93/0x190
Jan 31 12:18:37 p-pbs kernel:  drm_client_modeset_commit_atomic+0xb9/0x240
Jan 31 12:18:37 p-pbs kernel:  drm_client_modeset_commit_locked+0x5b/0x170
Jan 31 12:18:37 p-pbs kernel:  ? mutex_lock+0x12/0x50
Jan 31 12:18:37 p-pbs kernel:  drm_fb_helper_pan_display+0x113/0x280
Jan 31 12:18:37 p-pbs kernel:  fb_pan_display+0x8b/0x160
Jan 31 12:18:37 p-pbs kernel:  bit_update_start+0x20/0x50
Jan 31 12:18:37 p-pbs kernel:  fbcon_switch+0x469/0x620
Jan 31 12:18:37 p-pbs kernel:  csi_J+0x2a7/0x2f0
Jan 31 12:18:37 p-pbs kernel:  do_con_write+0x1405/0x2450
Jan 31 12:18:37 p-pbs kernel:  con_write+0x14/0x50
Jan 31 12:18:37 p-pbs kernel:  n_tty_write+0x154/0x550
Jan 31 12:18:37 p-pbs kernel:  ? __pfx_woken_wake_function+0x10/0x10
Jan 31 12:18:37 p-pbs kernel:  file_tty_write.isra.0+0x181/0x2d0
Jan 31 12:18:37 p-pbs kernel:  tty_write+0x11/0x20
Jan 31 12:18:37 p-pbs kernel:  vfs_write+0x274/0x490
Jan 31 12:18:37 p-pbs kernel:  ? _raw_spin_unlock+0xe/0x40
Jan 31 12:18:37 p-pbs kernel:  ksys_write+0x6f/0xf0
Jan 31 12:18:37 p-pbs kernel:  __x64_sys_write+0x19/0x30
Jan 31 12:18:37 p-pbs kernel:  x64_sys_call+0x79/0x2330
Jan 31 12:18:37 p-pbs kernel:  do_syscall_64+0x80/0xa30
Jan 31 12:18:37 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:18:37 p-pbs kernel:  ? x64_sys_call+0x1742/0x2330
Jan 31 12:18:37 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:18:37 p-pbs kernel:  ? do_syscall_64+0xb8/0xa30
Jan 31 12:18:37 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:18:37 p-pbs kernel:  ? __x64_sys_read+0x19/0x30
Jan 31 12:18:37 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:18:37 p-pbs kernel:  ? x64_sys_call+0x1e95/0x2330
Jan 31 12:18:37 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:18:37 p-pbs kernel:  ? do_syscall_64+0xb8/0xa30
Jan 31 12:18:37 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:18:37 p-pbs kernel:  ? x64_sys_call+0x1151/0x2330
Jan 31 12:18:37 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:18:37 p-pbs kernel:  ? do_syscall_64+0xb8/0xa30
Jan 31 12:18:37 p-pbs kernel:  ? exc_page_fault+0x90/0x1b0
Jan 31 12:18:37 p-pbs kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Jan 31 12:18:37 p-pbs kernel: RIP: 0033:0x79d02ba9a687
Jan 31 12:18:37 p-pbs kernel: RSP: 002b:00007ffca6436320 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Jan 31 12:18:37 p-pbs kernel: RAX: ffffffffffffffda RBX: 000079d02c04fe00 RCX: 000079d02ba9a687
Jan 31 12:18:37 p-pbs kernel: RDX: 000000000000000c RSI: 000079d02bf27cc4 RDI: 000000000000003e
Jan 31 12:18:37 p-pbs kernel: RBP: 000000000000003e R08: 0000000000000000 R09: 0000000000000000
Jan 31 12:18:37 p-pbs kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 00000000000186a0
Jan 31 12:18:37 p-pbs kernel: R13: 0000008c83613c66 R14: 000000000000000c R15: 000000000000003e
Jan 31 12:18:37 p-pbs kernel:  </TASK>
Jan 31 12:18:37 p-pbs kernel: INFO: task systemd:1 is blocked on a mutex likely owned by task kworker/1:2:2220351.
Jan 31 12:18:37 p-pbs kernel: task:kworker/1:2     state:D stack:0     pid:2220351 tgid:2220351 ppid:2      task_flags:0x4208060 flags:0x00004000
Jan 31 12:18:37 p-pbs kernel: Workqueue: events drm_fb_helper_damage_work
Jan 31 12:18:37 p-pbs kernel: Call Trace:
Jan 31 12:18:37 p-pbs kernel:  <TASK>
Jan 31 12:18:37 p-pbs kernel:  __schedule+0x468/0x1310
Jan 31 12:18:37 p-pbs kernel:  ? lock_timer_base+0x73/0xa0
Jan 31 12:18:37 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:18:37 p-pbs kernel:  ? _raw_spin_unlock_irqrestore+0x11/0x60
Jan 31 12:18:37 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:18:37 p-pbs kernel:  schedule+0x27/0xf0
Jan 31 12:18:37 p-pbs kernel:  schedule_timeout+0x89/0x110
Jan 31 12:18:37 p-pbs kernel:  ? __pfx_process_timeout+0x10/0x10
Jan 31 12:18:37 p-pbs kernel:  qxl_fence_wait+0xfc/0x1c0 [qxl]
Jan 31 12:18:37 p-pbs kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Jan 31 12:18:37 p-pbs kernel:  dma_fence_wait_timeout+0x67/0x170
Jan 31 12:18:37 p-pbs kernel:  dma_resv_wait_timeout+0xbc/0x1e0
Jan 31 12:18:37 p-pbs kernel:  ttm_bo_wait_ctx+0x53/0x90 [ttm]
Jan 31 12:18:37 p-pbs kernel:  qxl_bo_move+0x4f/0x110 [qxl]
Jan 31 12:18:37 p-pbs kernel:  ttm_bo_handle_move_mem+0xd3/0x1b0 [ttm]
Jan 31 12:18:37 p-pbs kernel:  ttm_bo_evict+0x135/0x190 [ttm]
Jan 31 12:18:37 p-pbs kernel:  ttm_bo_evict_cb+0x9a/0x110 [ttm]
Jan 31 12:18:37 p-pbs kernel:  ttm_lru_walk_for_evict+0xc0/0x230 [ttm]
Jan 31 12:18:37 p-pbs kernel:  ttm_bo_alloc_resource+0x1ce/0x5e0 [ttm]
Jan 31 12:18:37 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:18:37 p-pbs kernel:  ttm_bo_validate+0x9a/0x180 [ttm]
Jan 31 12:18:37 p-pbs kernel:  ttm_bo_init_reserved+0x157/0x1c0 [ttm]
Jan 31 12:18:37 p-pbs kernel:  qxl_bo_create+0x177/0x240 [qxl]
Jan 31 12:18:37 p-pbs kernel:  ? __pfx_qxl_ttm_bo_destroy+0x10/0x10 [qxl]
Jan 31 12:18:37 p-pbs kernel:  qxl_alloc_bo_reserved+0x4b/0xc0 [qxl]
Jan 31 12:18:37 p-pbs kernel:  qxl_image_alloc_objects+0x102/0x1c0 [qxl]
Jan 31 12:18:37 p-pbs kernel:  qxl_draw_dirty_fb+0x1be/0x530 [qxl]
Jan 31 12:18:37 p-pbs kernel:  ? ww_mutex_lock_interruptible+0x30/0x100
Jan 31 12:18:37 p-pbs kernel:  qxl_framebuffer_surface_dirty+0x10c/0x1f0 [qxl]
Jan 31 12:18:37 p-pbs kernel:  drm_fbdev_ttm_helper_fb_dirty+0x2ef/0x3ab [drm_ttm_helper]
Jan 31 12:18:37 p-pbs kernel:  drm_fb_helper_damage_work+0x92/0x180
Jan 31 12:18:37 p-pbs kernel:  process_one_work+0x18b/0x370
Jan 31 12:18:37 p-pbs kernel:  worker_thread+0x33a/0x480
Jan 31 12:18:37 p-pbs kernel:  ? _raw_spin_unlock_irqrestore+0x11/0x60
Jan 31 12:18:37 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:18:37 p-pbs kernel:  ? __pfx_worker_thread+0x10/0x10
Jan 31 12:18:37 p-pbs kernel:  kthread+0x10b/0x220
Jan 31 12:18:37 p-pbs kernel:  ? _raw_spin_unlock_irq+0xe/0x60
Jan 31 12:18:37 p-pbs kernel:  ? __pfx_kthread+0x10/0x10
Jan 31 12:18:37 p-pbs kernel:  ret_from_fork+0x208/0x240
Jan 31 12:18:37 p-pbs kernel:  ? __pfx_kthread+0x10/0x10
Jan 31 12:18:37 p-pbs kernel:  ret_from_fork_asm+0x1a/0x30
Jan 31 12:18:37 p-pbs kernel:  </TASK>
Jan 31 12:18:41 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:18:57 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:19:12 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:19:27 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:19:43 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:19:58 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:20:13 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:20:29 p-pbs kernel: [TTM] Buffer eviction failed
Jan 31 12:20:40 p-pbs kernel: INFO: task systemd:1 blocked for more than 245 seconds.
Jan 31 12:20:40 p-pbs kernel:       Tainted: P           O        6.17.4-2-pve #1
Jan 31 12:20:40 p-pbs kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 31 12:20:40 p-pbs kernel: task:systemd         state:D stack:0     pid:1     tgid:1     ppid:0      task_flags:0x400100 flags:0x00004002
Jan 31 12:20:40 p-pbs kernel: Call Trace:
Jan 31 12:20:40 p-pbs kernel:  <TASK>
Jan 31 12:20:40 p-pbs kernel:  __schedule+0x468/0x1310
Jan 31 12:20:40 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:20:40 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:20:40 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:20:40 p-pbs kernel:  ? add_wait_queue+0x76/0xa0
Jan 31 12:20:40 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:20:40 p-pbs kernel:  schedule+0x27/0xf0
Jan 31 12:20:40 p-pbs kernel:  schedule_preempt_disabled+0x15/0x30
Jan 31 12:20:40 p-pbs kernel:  __ww_mutex_lock.constprop.0+0x7fd/0xda0
Jan 31 12:20:40 p-pbs kernel:  __ww_mutex_lock_slowpath+0x16/0x30
Jan 31 12:20:40 p-pbs kernel:  ww_mutex_lock+0xec/0x100
Jan 31 12:20:40 p-pbs kernel:  drm_modeset_lock+0x5f/0xf0
Jan 31 12:20:40 p-pbs kernel:  drm_atomic_get_plane_state+0x93/0x190
Jan 31 12:20:40 p-pbs kernel:  drm_client_modeset_commit_atomic+0xb9/0x240
Jan 31 12:20:40 p-pbs kernel:  drm_client_modeset_commit_locked+0x5b/0x170
Jan 31 12:20:40 p-pbs kernel:  ? mutex_lock+0x12/0x50
Jan 31 12:20:40 p-pbs kernel:  drm_fb_helper_pan_display+0x113/0x280
Jan 31 12:20:40 p-pbs kernel:  fb_pan_display+0x8b/0x160
Jan 31 12:20:40 p-pbs kernel:  bit_update_start+0x20/0x50
Jan 31 12:20:40 p-pbs kernel:  fbcon_switch+0x469/0x620
Jan 31 12:20:40 p-pbs kernel:  csi_J+0x2a7/0x2f0
Jan 31 12:20:40 p-pbs kernel:  do_con_write+0x1405/0x2450
Jan 31 12:20:40 p-pbs kernel:  con_write+0x14/0x50
Jan 31 12:20:40 p-pbs kernel:  n_tty_write+0x154/0x550
Jan 31 12:20:40 p-pbs kernel:  ? __pfx_woken_wake_function+0x10/0x10
Jan 31 12:20:40 p-pbs kernel:  file_tty_write.isra.0+0x181/0x2d0
Jan 31 12:20:40 p-pbs kernel:  tty_write+0x11/0x20
Jan 31 12:20:40 p-pbs kernel:  vfs_write+0x274/0x490
Jan 31 12:20:40 p-pbs kernel:  ? _raw_spin_unlock+0xe/0x40
Jan 31 12:20:40 p-pbs kernel:  ksys_write+0x6f/0xf0
Jan 31 12:20:40 p-pbs kernel:  __x64_sys_write+0x19/0x30
Jan 31 12:20:40 p-pbs kernel:  x64_sys_call+0x79/0x2330
Jan 31 12:20:40 p-pbs kernel:  do_syscall_64+0x80/0xa30
Jan 31 12:20:40 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:20:40 p-pbs kernel:  ? x64_sys_call+0x1742/0x2330
Jan 31 12:20:40 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:20:40 p-pbs kernel:  ? do_syscall_64+0xb8/0xa30
Jan 31 12:20:40 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:20:40 p-pbs kernel:  ? __x64_sys_read+0x19/0x30
Jan 31 12:20:40 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:20:40 p-pbs kernel:  ? x64_sys_call+0x1e95/0x2330
Jan 31 12:20:40 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:20:40 p-pbs kernel:  ? do_syscall_64+0xb8/0xa30
Jan 31 12:20:40 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:20:40 p-pbs kernel:  ? x64_sys_call+0x1151/0x2330
Jan 31 12:20:40 p-pbs kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 31 12:20:40 p-pbs kernel:  ? do_syscall_64+0xb8/0xa30
Jan 31 12:20:40 p-pbs kernel:  ? exc_page_fault+0x90/0x1b0
Jan 31 12:20:40 p-pbs kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Jan 31 12:20:40 p-pbs kernel: RIP: 0033:0x79d02ba9a687
Jan 31 12:20:40 p-pbs kernel: RSP: 002b:00007ffca6436320 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Jan 31 12:20:40 p-pbs kernel: RAX: ffffffffffffffda RBX: 000079d02c04fe00 RCX: 000079d02ba9a687
Jan 31 12:20:40 p-pbs kernel: RDX: 000000000000000c RSI: 000079d02bf27cc4 RDI: 000000000000003e
Jan 31 12:20:40 p-pbs kernel: RBP: 000000000000003e R08: 0000000000000000 R09: 0000000000000000
Jan 31 12:20:40 p-pbs kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 00000000000186a0
Jan 31 12:20:40 p-pbs kernel: R13: 0000008c83613c66 R14: 000000000000000c R15: 000000000000003e
Jan 31 12:20:40 p-pbs kernel:  </TASK>
Jan 31 12:20:40 p-pbs kernel: INFO: task systemd:1 is blocked on a mutex likely owned by task kworker/1:2:2220351.
Jan 31 12:20:40 p-pbs kernel: task:kworker/1:2     state:D stack:0     pid:2220351 tgid:2220351 ppid:2      task_flags:0x4208060 flags:0x00004000
Jan 31 12:20:40 p-pbs kernel: Workqueue: events drm_fb_helper_damage_work
Jan 31 12:20:40 p-pbs kernel: Call Trace:
Jan 31 12:20:40 p-pbs kernel:  <TASK>

Jemand zufällig eine Idee?



Grüße
 
Kannst du den Backup Task Log und qm config VMID teilen? Was nutzt du als Datastore Ziel in PBS? Scheint wohl etwas mit der Grafik zu tun zu haben aber mehr Infos geben ein besseres Bild.
 
Last edited:
qm config
Code: 
agent: 1
boot: order=scsi0;ide2
cores: 2
cpu: host,flags=+aes
description: ansible%3A production\%0ADebian%3A 13 Trixie\%0ARun Check_Mk 2.4
ide2: none,media=cdrom
memory: 6144
name: p-pbs
net0: virtio=5A:4C:1B:2A:51:AD,bridge=vmbr40
numa: 0
onboot: 1
ostype: l26
scsi0: Data:vm-209-disk-0,cache=writeback,iothread=1,size=15G,ssd=1
scsi2: Data:vm-209-disk-2,backup=0,cache=writeback,iothread=1,size=500G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=361fe595-0a2a-450f-8d70-9877670893c9
sockets: 1
startup: order=4,up=60
tags: 
unused0: Data:vm-209-disk-1
vga: qxl,memory=4

Der PBS verwendet als Datastore ein Single ZFS.

Noch einmal kurz erklärt. Ich will den PBS über den PVE auf ein lokales Backup 'Storage vom PVE mittels STOP Mode sichern.


Das lief Jahre lang, auch noch unter 8.4.x und dann auf einmal innerhalb der 8.4er Version plötzlich der Fehler

Unten stehend mal das Log vom Backup Task

Code: 
INFO: starting new backup job: vzdump 209 --mode stop --quiet 1 --notes-template '{{guestname}}, {{vmid}}' --fleecing 0 --compress zstd --mailnotification always --prune-backups 'keep-last=4' --storage Backup --notification-mode notification-system
INFO: Starting Backup of VM 209 (qemu)
INFO: Backup started at 2026-01-31 12:15:05
INFO: status = running
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: p-pbs
INFO: include disk 'scsi0' 'Data:vm-209-disk-0' 15G
INFO: exclude disk 'scsi2' 'Data:vm-209-disk-2' (backup=no)
INFO: stopping virtual guest
INFO: VM quit/powerdown failed
ERROR: Backup of VM 209 failed - command 'qm shutdown 209 --skiplock --keepActive --timeout 600' failed: exit code 255
INFO: Failed at 2026-01-31 12:25:06
INFO: Backup job finished with errors
INFO: notified via target `mail-to-marko`
TASK ERROR: job errors
 
Kannst du mal probieren die Grafik auf default zu stellen? Gab es einen Grund davon abzuweichen?
Ich fand viel Relation zu QXL bei der Recherche nach [TTM] Buffer eviction failed.
 
Das Problem taucht wohl auch erst nach etwas längerem laufen der VM auf. Wenn ich Samstag komplett ausschalte und wieder an mache und Montag auf Shutdown über das PVE gehe dann klappt es mit dem runter fahren. Ich habe den Spice Treiber genommen weil ich mich früher mal mittels der Spice Console mit dem Terminal des PBS verbunden hatte.

Ich habe jetzt mal auf default gestellt.
 
CoolTux said:
qm config
Code: 
agent: 1
boot: order=scsi0;ide2
cores: 2
cpu: host,flags=+aes
description: ansible%3A production\%0ADebian%3A 13 Trixie\%0ARun Check_Mk 2.4
ide2: none,media=cdrom
memory: 6144
name: p-pbs
net0: virtio=5A:4C:1B:2A:51:AD,bridge=vmbr40
numa: 0
onboot: 1
ostype: l26
scsi0: Data:vm-209-disk-0,cache=writeback,iothread=1,size=15G,ssd=1
scsi2: Data:vm-209-disk-2,backup=0,cache=writeback,iothread=1,size=500G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=361fe595-0a2a-450f-8d70-9877670893c9
sockets: 1
startup: order=4,up=60
tags:
unused0: Data:vm-209-disk-1
vga: qxl,memory=4

Der PBS verwendet als Datastore ein Single ZFS.

Noch einmal kurz erklärt. Ich will den PBS über den PVE auf ein lokales Backup 'Storage vom PVE mittels STOP Mode sichern.


Das lief Jahre lang, auch noch unter 8.4.x und dann auf einmal innerhalb der 8.4er Version plötzlich der Fehler

Unten stehend mal das Log vom Backup Task

Code: 
INFO: starting new backup job: vzdump 209 --mode stop --quiet 1 --notes-template '{{guestname}}, {{vmid}}' --fleecing 0 --compress zstd --mailnotification always --prune-backups 'keep-last=4' --storage Backup --notification-mode notification-system
INFO: Starting Backup of VM 209 (qemu)
INFO: Backup started at 2026-01-31 12:15:05
INFO: status = running
INFO: backup mode: stop
INFO: ionice priority: 7
INFO: VM Name: p-pbs
INFO: include disk 'scsi0' 'Data:vm-209-disk-0' 15G
INFO: exclude disk 'scsi2' 'Data:vm-209-disk-2' (backup=no)
INFO: stopping virtual guest
INFO: VM quit/powerdown failed
ERROR: Backup of VM 209 failed - command 'qm shutdown 209 --skiplock --keepActive --timeout 600' failed: exit code 255
INFO: Failed at 2026-01-31 12:25:06
INFO: Backup job finished with errors
INFO: notified via target `mail-to-marko`
TASK ERROR: job errors
Click to expand...
Single ZFS was ist damit gement?

ist der qemu guest agent installiert?
# https://pve.proxmox.com/wiki/Qemu-guest-agent

Ich habe auch einen Server mit Virtualisierung über Proxmox VE, der Proxmox BS ist als LXContainer installiert und arbeitet wir erwartet!
 
Ich sehe gerade, das ist noch eine Rest "unused0: Data:vm-209-disk-1" aus alten Zeiten übrig.
Du könntest das mal aus der VM 209 Config löschen, z.b. mit nano.
Dann bliebe die vm-209-disk-1 erhalten.
Dann starte bitte mal neu die VM.
 
Warum machst du überhaupt ein Stop Backup?
Ich sichere meinen virtuellen PBS jeden Tag ganz normal per Snapshot als VZDump auf einen USB Stick. (Nur das OS, ohne Datendisks)
Solange da gerade kein Backupjob oder Update läuft, kann selbst bei einem "Inkonsistenten" Backup nichts inkonsistent gehen.
 
  • Like
Reactions: Johannes S and CoolTux
Falk R. said:
Warum machst du überhaupt ein Stop Backup?
Ich sichere meinen virtuellen PBS jeden Tag ganz normal per Snapshot als VZDump auf einen USB Stick. (Nur das OS, ohne Datendisks)
Solange da gerade kein Backupjob oder Update läuft, kann selbst bei einem "Inkonsistenten" Backup nichts inkonsistent gehen.
Click to expand...

Ich habe damit vor Jahren mal so angefangen und es hat halt von Anfang an immer funktioniert. Wieso das dann ändern wollen :)

Übrigens soll ich schöne Grüße von Micha (Michael Maurer) ausrichten ;)
 
  • Like
Reactions: Johannes S and Falk R.
CoolTux said:
Ich habe damit vor Jahren mal so angefangen und es hat halt von Anfang an immer funktioniert. Wieso das dann ändern wollen :)

Übrigens soll ich schöne Grüße von Micha (Michael Maurer) ausrichten ;)
Click to expand...
Dankeschön
 
You must log in or register to reply here.
Top Bottom
Back