Hi, I've started using Proxmox about 6 months ago and have been loving it. Last night, I found that my Plex container was not responding. All other VMs and containers were fine (only 2 others on the machine). I was able to login via SSH and found the following in the journal:
It looks like there was an issue with ZFS, perhaps caused by Plex? The only way I could get the container to reset was with a hard reset of the system (container shutdown/stop, host restart/shutdown did not work).
Code:
Jan 13 01:24:13 pve1 kernel: BUG: unable to handle kernel paging request at ffffffffc03c3164
Jan 13 01:24:13 pve1 kernel: IP: avl_insert+0x4b/0xd0 [zavl]
Jan 13 01:24:13 pve1 kernel: PGD 49e40e067 P4D 49e40e067 PUD 49e410067 PMD 6312fd067 PTE 62e838061
Jan 13 01:24:13 pve1 kernel: Oops: 0003 [#1] SMP PTI
Jan 13 01:24:13 pve1 kernel: Modules linked in: tcp_diag inet_diag binfmt_misc veth ip_set ip6table_filter ip6_tables cmac arc4 md4 nls_utf8 cifs ccm fscache iptable_filter softdog nfnetlink_log nfnetlink ast intel_powerclamp ttm coretem
Jan 13 01:24:13 pve1 kernel: e1000e(O) i2c_i801 libahci ptp pps_core
Jan 13 01:24:13 pve1 kernel: CPU: 14 PID: 9883 Comm: Plex Media Serv Tainted: P W IO 4.15.18-7-pve #1
Jan 13 01:24:13 pve1 kernel: Hardware name: ASUS RS700-E6-RS4/Z8PS-D12-1U, BIOS 0401 01/22/2009
Jan 13 01:24:13 pve1 kernel: RIP: 0010:avl_insert+0x4b/0xd0 [zavl]
Jan 13 01:24:13 pve1 kernel: RSP: 0018:ffffb98d6a11bce0 EFLAGS: 00010282
Jan 13 01:24:13 pve1 kernel: RAX: 0000000000000000 RBX: ffffa09b6cd21600 RCX: ffffffffc03c3165
Jan 13 01:24:13 pve1 kernel: RDX: 0000000000000000 RSI: ffffa09b6cd21608 RDI: ffffa096bf2af948
Jan 13 01:24:13 pve1 kernel: RBP: ffffb98d6a11bd30 R08: ffffffffc03c3164 R09: ffffa09873807180
Jan 13 01:24:13 pve1 kernel: R10: ffffa09b6cd21600 R11: ffffa0981d6071c0 R12: ffffa096bf2af918
Jan 13 01:24:13 pve1 kernel: R13: ffffffffc03c315c R14: 0000000000000000 R15: 0000000000000000
Jan 13 01:24:13 pve1 kernel: FS: 00007fd795bff700(0000) GS:ffffa09873dc0000(0000) knlGS:0000000000000000
Jan 13 01:24:13 pve1 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 13 01:24:13 pve1 kernel: CR2: ffffffffc03c3164 CR3: 00000005f56b6000 CR4: 00000000000026e0
Jan 13 01:24:13 pve1 kernel: Call Trace:
Jan 13 01:24:13 pve1 kernel: ? zfs_range_lock+0x4bf/0x5c0 [zfs]
Jan 13 01:24:13 pve1 kernel: ? spl_kmem_zalloc+0xa4/0x190 [spl]
Jan 13 01:24:13 pve1 kernel: ? spl_kmem_zalloc+0xa4/0x190 [spl]
Jan 13 01:24:13 pve1 kernel: zfs_get_data+0x1b5/0x2a0 [zfs]
Jan 13 01:24:13 pve1 kernel: zil_commit.part.14+0x451/0x8b0 [zfs]
Jan 13 01:24:13 pve1 kernel: zil_commit+0x17/0x20 [zfs]
Jan 13 01:24:13 pve1 kernel: zfs_fsync+0x77/0xf0 [zfs]
Jan 13 01:24:13 pve1 kernel: zpl_fsync+0x68/0xa0 [zfs]
Jan 13 01:24:13 pve1 kernel: vfs_fsync_range+0x51/0xb0
Jan 13 01:24:13 pve1 kernel: do_fsync+0x3d/0x70
Jan 13 01:24:13 pve1 kernel: SyS_fdatasync+0x13/0x20
Jan 13 01:24:13 pve1 kernel: do_syscall_64+0x73/0x130
Jan 13 01:24:13 pve1 kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Jan 13 01:24:13 pve1 kernel: RIP: 0033:0x7fd7ec76e2e7
Jan 13 01:24:13 pve1 kernel: RSP: 002b:00007fd795bfd7e0 EFLAGS: 00000293 ORIG_RAX: 000000000000004b
Jan 13 01:24:13 pve1 kernel: RAX: ffffffffffffffda RBX: 000000000000000a RCX: 00007fd7ec76e2e7
Jan 13 01:24:13 pve1 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000000000000a
Jan 13 01:24:13 pve1 kernel: RBP: 00007fd795bfd820 R08: 0000000000000000 R09: 0000000000000022
Jan 13 01:24:13 pve1 kernel: R10: 00007fd795bfe740 R11: 0000000000000293 R12: 00000000000000e4
Jan 13 01:24:13 pve1 kernel: R13: 0000000000f55608 R14: 0000000000000001 R15: 0000000000989680
Jan 13 01:24:13 pve1 kernel: Code: 89 c1 83 e0 04 48 83 c9 01 48 09 c8 4d 85 c0 48 c7 06 00 00 00 00 48 c7 46 08 00 00 00 00 48 89 46 10 0f 84 84 00 00 00 48 63 c2 <49> 89 34 c0 49 8b 50 10 8b 04 85 70 71 42 c0 89 d1 83 e1 03 83
Jan 13 01:24:13 pve1 kernel: RIP: avl_insert+0x4b/0xd0 [zavl] RSP: ffffb98d6a11bce0
Jan 13 01:24:13 pve1 kernel: CR2: ffffffffc03c3164
Jan 13 01:24:13 pve1 kernel: ---[ end trace 2d3ba7e57c5ba825 ]---
It looks like there was an issue with ZFS, perhaps caused by Plex? The only way I could get the container to reset was with a hard reset of the system (container shutdown/stop, host restart/shutdown did not work).