had today a kernel panic - PANIC at zfs_znode.c:620:zfs_znode_alloc()

tebers

Member
Dec 12, 2021
4
0
6
59
I thought I should report :

host has ecc-ram

Code:
Jun 15 14:03:20 pve kernel: VERIFY3(insert_inode_locked(ip) == 0) failed (-16 == 0)
Jun 15 14:03:20 pve kernel: PANIC at zfs_znode.c:620:zfs_znode_alloc()
Jun 15 14:03:20 pve kernel: Showing stack for process 933423
Jun 15 14:03:20 pve kernel: CPU: 3 PID: 933423 Comm: lpqd Tainted: P           O      5.15.35-2-pve #1
Jun 15 14:03:20 pve kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570D4U-2L2T, BIOS P1.40 05/19/2021
Jun 15 14:03:20 pve kernel: Call Trace:
Jun 15 14:03:20 pve kernel:  <TASK>
Jun 15 14:03:20 pve kernel:  dump_stack_lvl+0x4a/0x5f
Jun 15 14:03:20 pve kernel:  dump_stack+0x10/0x12
Jun 15 14:03:20 pve kernel:  spl_dumpstack+0x29/0x2b [spl]
Jun 15 14:03:20 pve kernel:  spl_panic+0xd1/0xe9 [spl]
Jun 15 14:03:20 pve kernel:  ? spl_kmem_cache_alloc+0xb4/0x790 [spl]
Jun 15 14:03:20 pve kernel:  ? spl_kmem_cache_alloc+0x79/0x790 [spl]
Jun 15 14:03:20 pve kernel:  ? lz4_decompress_zfs+0x2a6/0x330 [zfs]
Jun 15 14:03:20 pve kernel:  ? __cond_resched+0x1a/0x50
Jun 15 14:03:20 pve kernel:  ? iput.part.0+0x61/0x1d0
Jun 15 14:03:20 pve kernel:  ? insert_inode_locked+0x204/0x210
Jun 15 14:03:20 pve kernel:  zfs_znode_alloc+0x622/0x760 [zfs]
Jun 15 14:03:20 pve kernel:  zfs_mknode+0x7db/0xef0 [zfs]
Jun 15 14:03:20 pve kernel:  zfs_create+0x657/0x970 [zfs]
Jun 15 14:03:20 pve kernel:  zpl_mknod+0xbc/0x1c0 [zfs]
Jun 15 14:03:20 pve kernel:  vfs_mknod+0xa3/0x1b0
Jun 15 14:03:20 pve kernel:  unix_bind+0x2dd/0x4d0
Jun 15 14:03:20 pve kernel:  __sys_bind+0xe6/0x110
Jun 15 14:03:20 pve kernel:  ? syscall_trace_enter.constprop.0+0xa0/0x1c0
Jun 15 14:03:20 pve kernel:  __x64_sys_bind+0x1a/0x20
Jun 15 14:03:20 pve kernel:  do_syscall_64+0x5c/0xc0
Jun 15 14:03:20 pve kernel:  ? exit_to_user_mode_prepare+0x37/0x1b0
Jun 15 14:03:20 pve kernel:  ? syscall_exit_to_user_mode+0x27/0x50
Jun 15 14:03:20 pve kernel:  ? do_syscall_64+0x69/0xc0
Jun 15 14:03:20 pve kernel:  ? irqentry_exit_to_user_mode+0x9/0x20
Jun 15 14:03:20 pve kernel:  ? irqentry_exit+0x19/0x30
Jun 15 14:03:20 pve kernel:  ? exc_page_fault+0x89/0x160
Jun 15 14:03:20 pve kernel:  ? asm_exc_page_fault+0x8/0x30
Jun 15 14:03:20 pve kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
Jun 15 14:03:20 pve kernel: RIP: 0033:0x7f197f98be47
Jun 15 14:03:20 pve kernel: Code: ff ff ff ff c3 66 0f 1f 44 00 00 48 8b 15 41 f0 0b 00 f7 d8 64 89 02 b8 ff ff ff ff eb bc 0f 1f 44 00 00 b8 31 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 19 f0 0b 00 f7 d8 64 89 01 48
Jun 15 14:03:20 pve kernel: RSP: 002b:00007ffdcaa1f038 EFLAGS: 00000213 ORIG_RAX: 0000000000000031
Jun 15 14:03:20 pve kernel: RAX: ffffffffffffffda RBX: 000055afac7b92b0 RCX: 00007f197f98be47
Jun 15 14:03:20 pve kernel: RDX: 000000000000006e RSI: 00007ffdcaa1f090 RDI: 0000000000000006
Jun 15 14:03:20 pve kernel: RBP: 000055afac7bf280 R08: 0000000000000000 R09: 00007ffdcaa1eed0
Jun 15 14:03:20 pve kernel: R10: 00007ffdcaa1ed75 R11: 0000000000000213 R12: 0000000000000005
Jun 15 14:03:20 pve kernel: R13: 00007ffdcaa1f170 R14: 00007ffdcaa1f092 R15: 00007ffdcaa1f100
Jun 15 14:03:20 pve kernel:  </TASK>


Code:
root@pve:~# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.35-2-pve)
pve-manager: 7.2-4 (running version: 7.2-4/ca9d43cc)
pve-kernel-5.15: 7.2-4
pve-kernel-helper: 7.2-4
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.15.30-2-pve: 5.15.30-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-2
libpve-storage-perl: 7.2-4
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.3-1
proxmox-backup-file-restore: 2.2.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-10
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1

Code:
root@pve:~# lscpu
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   48 bits physical, 48 bits virtual
CPU(s):                          24
On-line CPU(s) list:             0-23
Thread(s) per core:              2
Core(s) per socket:              12
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       AuthenticAMD
CPU family:                      25
Model:                           33
Model name:                      AMD Ryzen 9 5900X 12-Core Processor
Stepping:                        2
Frequency boost:                 enabled
CPU MHz:                         3700.000
CPU max MHz:                     4950.1948
CPU min MHz:                     2200.0000
BogoMIPS:                        7386.17
Virtualization:                  AMD-V
L1d cache:                       384 KiB
L1i cache:                       384 KiB
L2 cache:                        6 MiB
L3 cache:                        64 MiB
NUMA node0 CPU(s):               0-23
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Retpolines, IBPB conditional, IBRS_FW, STIBP always-on, RSB filling
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc re
                                 p_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_l
                                 egacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_
                                 l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 
                                 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasi
                                 d decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip pku ospke vaes vpclmulqdq rdpid overflow_recov succor smca fsrm
[ICODE]
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!