Tainted P

[C8Z06]

Hi all. First of all, I have been LOVING Proxmox. It all started when my primary PC gave up the ghost which brought down my entire life lol. I researched and found Proxmox and spent my whole beach vacation this past spring holed up in a bedroom with laptops and hard drives all over the place installing and learning. Since then I have 6 VM's including LSI PCI pass through of 12 14TB hard drives to a TrueNAS VM.

The problem is I tend to be more of a starter than a maintainer (I am working on that). I have been thinking for weeks "I MUST start looking for videos to learn about how to monitor and maintain Proxmox". Just last night I started googling and reading. This morning I wake up to find several messages on my terminal, and some small amount of unresponsiveness in my panel (my backup job from last night is stuck for one thing)

THE ASK:

1. Can you guys point me to what I should do from here with this particular "Tainted P" issue (and do you think that is related to my backup being hung?)

2. Can you please point me to some "go to" resources in the way of videos that do a good job of teaching me how to "monitor and maintain". I have a desire to learn but just need a little help getting pointed in the right direction.

3. I would like a referral to someone that does paid tech support. If I ever REALLY get in a bind and am not sure what to do next, and am too busy in life to take the time to figure it out, it would make me feel better knowing I could reach out to someone that could bail me out.

THANK YOU!

Nov 11 05:18:41 prox1 kernel: CIFS: VFS: Send error in write = -11
Nov 11 05:21:55 prox1 kernel: INFO: task task UPID:prox1:740775 blocked for more than 120 seconds.
Nov 11 05:21:56 prox1 kernel:       Tainted: P           O      5.15.53-1-pve #1
Nov 11 05:21:56 prox1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 11 05:21:56 prox1 kernel: task:task UPID:prox1 state:D stack:    0 pid:740775 ppid:     1 flags:0x00004000
Nov 11 05:21:56 prox1 kernel: Call Trace:
Nov 11 05:21:56 prox1 kernel:  <TASK>
Nov 11 05:21:56 prox1 kernel:  __schedule+0x33d/0x1750
Nov 11 05:21:56 prox1 kernel:  ? txg_list_add+0x79/0xa0 [zfs]
Nov 11 05:21:56 prox1 kernel:  ? __mod_memcg_lruvec_state+0x63/0xe0
Nov 11 05:21:56 prox1 kernel:  schedule+0x4e/0xc0
Nov 11 05:21:56 prox1 kernel:  io_schedule+0x46/0x80
Nov 11 05:21:56 prox1 kernel:  wait_on_page_bit_common+0x114/0x3e0
Nov 11 05:21:56 prox1 kernel:  ? filemap_invalidate_unlock_two+0x50/0x50
Nov 11 05:21:56 prox1 kernel:  wait_on_page_bit+0x3f/0x50
Nov 11 05:21:56 prox1 kernel:  wait_on_page_writeback+0x26/0x80
Nov 11 05:21:56 prox1 kernel:  cifs_writepages+0x5f1/0xc50 [cifs]
Nov 11 05:21:56 prox1 kernel:  do_writepages+0xd5/0x210
Nov 11 05:21:56 prox1 kernel:  ? migrate_vma_check_page+0xc0/0xc0
Nov 11 05:21:56 prox1 kernel:  ? task_numa_fault+0x5c6/0xc10
Nov 11 05:21:56 prox1 kernel:  filemap_fdatawrite_wbc+0x89/0xe0
Nov 11 05:21:56 prox1 kernel:  ? __bpf_trace_mm_migrate_pages_start+0x20/0x20
Nov 11 05:21:56 prox1 kernel:  filemap_write_and_wait_range+0x72/0xe0
Nov 11 05:21:56 prox1 kernel:  cifs_flush+0x67/0x100 [cifs]
Nov 11 05:21:56 prox1 kernel:  filp_close+0x37/0x70
Nov 11 05:21:56 prox1 kernel:  close_fd+0x38/0x60
Nov 11 05:21:56 prox1 kernel:  __x64_sys_close+0x12/0x50
Nov 11 05:21:56 prox1 kernel:  do_syscall_64+0x5c/0xc0
Nov 11 05:21:56 prox1 kernel:  ? exit_to_user_mode_prepare+0x37/0x1b0
Nov 11 05:21:56 prox1 kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
Nov 11 05:21:56 prox1 kernel:  ? irqentry_exit+0x1d/0x30
Nov 11 05:21:56 prox1 kernel:  ? exc_page_fault+0x89/0x170
Nov 11 05:21:56 prox1 kernel:  entry_SYSCALL_64_after_hwframe+0x61/0xcb
Nov 11 05:21:56 prox1 kernel: RIP: 0033:0x7f46f0c840f3
Nov 11 05:21:56 prox1 kernel: RSP: 002b:00007ffd3a3fdec8 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
Nov 11 05:21:56 prox1 kernel: RAX: ffffffffffffffda RBX: 000055797863e2a0 RCX: 00007f46f0c840f3
Nov 11 05:21:56 prox1 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000000000c
Nov 11 05:21:56 prox1 kernel: RBP: 000000000000000c R08: 0000000000000000 R09: 0000000000000000
Nov 11 05:21:56 prox1 kernel: R10: 0000000000000001 R11: 0000000000000246 R12: 000055797e03cd70
Nov 11 05:21:56 prox1 kernel: R13: 0000000000000000 R14: 000055797dff96a0 R15: 0000000000000001
Nov 11 05:21:56 prox1 kernel:  </TASK>
Nov 11 05:21:56 prox1 kernel: INFO: task kworker/18:44:1155559 blocked for more than 120 seconds.
Nov 11 05:21:56 prox1 kernel:       Tainted: P           O      5.15.53-1-pve #1
Nov 11 05:21:56 prox1 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 11 05:21:56 prox1 kernel: task:kworker/18:44   state:D stack:    0 pid:1155559 ppid:     2 flags:0x00004000
Nov 11 05:21:56 prox1 kernel: Workqueue: cifsiod cifs_writev_complete [cifs]
Nov 11 05:21:56 prox1 kernel: Call Trace:
Nov 11 05:21:56 prox1 kernel:  <TASK>
Nov 11 05:21:56 prox1 kernel:  __schedule+0x33d/0x1750
Nov 11 05:21:56 prox1 kernel:  ? __mutex_unlock_slowpath.constprop.0+0x8e/0x120
Nov 11 05:21:56 prox1 kernel:  ? kmem_cache_free+0x24e/0x290
Nov 11 05:21:56 prox1 kernel:  ? mempool_free_slab+0x2/0x20
Nov 11 05:21:56 prox1 kernel:  schedule+0x4e/0xc0
Nov 11 05:21:56 prox1 kernel:  io_schedule+0x46/0x80
Nov 11 05:21:56 prox1 kernel:  wait_on_page_bit_common+0x114/0x3e0
Nov 11 05:21:56 prox1 kernel:  ? filemap_invalidate_unlock_two+0x50/0x50
Nov 11 05:21:56 prox1 kernel:  __lock_page+0x4c/0x60
Nov 11 05:21:56 prox1 kernel:  cifs_writev_complete+0x388/0x820 [cifs]
Nov 11 05:21:56 prox1 kernel:  process_one_work+0x22b/0x3d0
Nov 11 05:21:56 prox1 kernel:  worker_thread+0x53/0x420
Nov 11 05:21:56 prox1 kernel:  ? process_one_work+0x3d0/0x3d0
Nov 11 05:21:56 prox1 kernel:  kthread+0x12a/0x150
Nov 11 05:21:56 prox1 kernel:  ? set_kthread_struct+0x50/0x50
Nov 11 05:21:56 prox1 kernel:  ret_from_fork+0x22/0x30
Nov 11 05:21:56 prox1 kernel:  </TASK>

 

[C8Z06]

When I posted, it wouldn't allow me to put as much of the log as I wanted, so I am attaching it here.

 

[C8Z06]

A friend said I should prob get my tainted P checked out by a doctor. I said I was seeking the help of a Proxtologist hahahaha

 

[Jsingh]

What version of proxmox and kernel are you using ? Whats the platform?
I am having same issues with kernel 5.15 and 5.19, they are practically unusable with zfs pools. I switched back to 5.13 for me and it does not have these errors.
I am still trying to find out more.

 

[C8Z06]

What version of proxmox and kernel are you using ? Whats the platform?
I am having same issues with kernel 5.15 and 5.19, they are practically unusable with zfs pools. I switched back to 5.13 for me and it does not have these errors.
I am still trying to find out more.

proxmox-ve: 7.2-1 (running kernel: 5.15.64-1-pve).

I have not seen this happen again ... so I am not sure what the issue was.