Created
April 1, 2022 13:43
-
-
Save jaysonsantos/dfb76e9401ebb932bbfdb90734a4ebc8 to your computer and use it in GitHub Desktop.
This file has been truncated, but you can view the full file.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| -- Logs begin at Thu 2022-03-31 01:08:20 UTC, end at Fri 2022-04-01 13:43:38 UTC. -- | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Booting Linux on physical CPU 0x0000000000 [0x412fd050] | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Linux version 4.19.193-1001-rockchip-g12d0b2b258a3 (jayson@hp-proliant-dl160-g6-1) (gcc version 10.3.1 20210621 (GNU Toolchain for the A-profile Architecture 10.3-2021.07 (arm-10.29)), GNU ld (GNU Toolchain for the A-profile Architecture 10.3-2021.07 (arm-10.29)) 2.36.1.20210621) #rockchip SMP Thu Mar 31 13:27:16 UTC 2022 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Machine model: Radxa ROCK 3 Model A | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: OF: fdt: Reserved memory: failed to reserve memory for node 'drm-logo@00000000': base 0x0000000000000000, size 0 MiB | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: OF: fdt: Reserved memory: failed to reserve memory for node 'drm-cubic-lut@00000000': base 0x0000000000000000, size 0 MiB | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Reserved memory: created CMA memory pool at 0x00000001e0000000, size 512 MiB | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: OF: reserved mem: initialized node rknpu, compatible id shared-dma-pool | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: cma: Reserved 16 MiB at 0x00000000ef000000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: On node 0 totalpages: 2031104 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: DMA32 zone: 15352 pages used for memmap | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: DMA32 zone: 0 pages reserved | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: DMA32 zone: 982528 pages, LIFO batch:63 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Normal zone: 16384 pages used for memmap | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Normal zone: 1048576 pages, LIFO batch:63 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: psci: probing for conduit method from DT. | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: psci: PSCIv1.1 detected in firmware. | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: psci: Using standard PSCI v0.2 function IDs | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: psci: MIGRATE_INFO_TYPE not supported. | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: psci: SMC Calling Convention v1.2 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: percpu: Embedded 23 pages/cpu s55272 r8192 d30744 u94208 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: pcpu-alloc: s55272 r8192 d30744 u94208 alloc=23*4096 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Detected VIPT I-cache on CPU0 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: CPU features: detected: Virtualization Host Extensions | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: CPU features: detected: Speculative Store Bypassing Safe (SSBS) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Built 1 zonelists, mobility grouping on. Total pages: 1999368 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Kernel command line: initrd=initrd.img-4.19.193-1001-rockchip-g12d0b2b258a3 root=UUID=960abbce-6442-414f-81d8-3e7b7cd1ef60 rootwait rw rootfstype=ext4 console=tty1 console=ttyFIQ0,1500000 panic=10 consoleblank=0 loglevel=7 fsck.repair=yes cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mem auto-init: stack:off, heap alloc:off, heap free:off | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: software IO TLB: mapped [mem 0xeafff000-0xeefff000] (64MB) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Memory: 7338856K/8124416K available (12542K kernel code, 1826K rwdata, 4500K rodata, 1536K init, 1794K bss, 244888K reserved, 540672K cma-reserved) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: ftrace: allocating 46123 entries in 181 pages | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rcu: Hierarchical RCU implementation. | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rcu: RCU event tracing is enabled. | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rcu: RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: GICv3: GIC: Using split EOI/Deactivate mode | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: GICv3: Distributor has no Range Selector support | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: GICv3: no VLPI support, no direct LPI support | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: ITS [mem 0xfd440000-0xfd45ffff] | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: ITS@0x00000000fd440000: allocated 8192 Devices @210000 (indirect, esz 8, psz 64K, shr 0) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: ITS@0x00000000fd440000: allocated 32768 Interrupt Collections @220000 (flat, esz 2, psz 64K, shr 0) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: ITS: using cache flushing for cmd queue | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: GIC: using LPI property table @0x0000000000230000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: GICv3: CPU0: found redistributor 0 region 0:0x00000000fd460000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: CPU0: using LPI pending table @0x0000000000240000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: GIC: using cache flushing for LPI property table | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: random: random: get_random_bytes called from start_kernel+0x358/0x4e8 with crng_init=0 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: arch_timer: cp15 timer(s) running at 24.00MHz (phys). | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Console: colour dummy device 80x25 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: console [tty1] enabled | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=80000) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: pid_max: default: 32768 minimum: 301 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Mount-cache hash table entries: 16384 (order: 5, 131072 bytes) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: ASID allocator initialised with 32768 entries | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rcu: Hierarchical SRCU implementation. | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Platform MSI: interrupt-controller@fd440000 domain created | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: PCI/MSI: /interrupt-controller@fd400000/interrupt-controller@fd440000 domain created | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: smp: Bringing up secondary CPUs ... | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Detected VIPT I-cache on CPU1 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: GICv3: CPU1: found redistributor 100 region 0:0x00000000fd480000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: CPU1: using LPI pending table @0x0000000000250000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: CPU1: Booted secondary processor 0x0000000100 [0x412fd050] | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Detected VIPT I-cache on CPU2 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: GICv3: CPU2: found redistributor 200 region 0:0x00000000fd4a0000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: CPU2: using LPI pending table @0x0000000000260000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: CPU2: Booted secondary processor 0x0000000200 [0x412fd050] | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Detected VIPT I-cache on CPU3 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: GICv3: CPU3: found redistributor 300 region 0:0x00000000fd4c0000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: CPU3: using LPI pending table @0x0000000000270000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: CPU3: Booted secondary processor 0x0000000300 [0x412fd050] | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: smp: Brought up 1 node, 4 CPUs | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: SMP: Total of 4 processors activated. | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: CPU features: detected: GIC system register CPU interface | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: CPU features: detected: Privileged Access Never | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: CPU features: detected: LSE atomic instructions | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: CPU features: detected: User Access Override | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: CPU features: detected: 32-bit EL0 Support | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: CPU features: detected: RAS Extension Support | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: CPU: All CPU(s) started at EL2 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: alternatives: patching kernel code | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: devtmpfs: initialized | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Registered cp15_barrier emulation handler | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Registered setend emulation handler | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: futex hash table entries: 1024 (order: 4, 65536 bytes) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: pinctrl core: initialized pinctrl subsystem | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: regulator-dummy: no parameters | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: NET: Registered protocol family 16 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: cpuidle: using governor menu | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Registered FIQ tty driver | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: DMA: preallocated 256 KiB pool for atomic allocations | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: console [pstore-1] enabled | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: pstore: Registered ramoops as persistent store backend | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: ramoops: attached 0xf0000@0x110000, ecc: 0/0 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: platform fde40000.npu: assigned reserved memory node rknpu | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-gpio fdd60000.gpio: probed gpio0 (fdd60000.gpio) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-gpio fe740000.gpio: probed gpio1 (fe740000.gpio) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-gpio fe750000.gpio: probed gpio2 (fe750000.gpio) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-gpio fe760000.gpio: probed gpio3 (fe760000.gpio) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-gpio fe770000.gpio: probed gpio4 (fe770000.gpio) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-pinctrl pinctrl: probed pinctrl | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: cryptd: max_cpu_qlen set to 1000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: fbcon: Taking over console | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: dc_12v: 12000 mV | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: reg-fixed-voltage dc-12v: dc_12v supplying 12000000uV | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: vcc3v3_sys: 3300 mV | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: reg-fixed-voltage vcc3v3-sys: Looking up vin-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: vcc3v3_sys: supplied by dc_12v | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: reg-fixed-voltage vcc3v3-sys: vcc3v3_sys supplying 3300000uV | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: vcc5v0_sys: 5000 mV | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: reg-fixed-voltage vcc5v0-sys: Looking up vin-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: vcc5v0_sys: supplied by dc_12v | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: reg-fixed-voltage vcc5v0-sys: vcc5v0_sys supplying 5000000uV | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: vcc5v0_host: no parameters | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: reg-fixed-voltage vcc5v0-host-regulator: vcc5v0_host supplying 0uV | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: vcc5v0_otg: no parameters | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: reg-fixed-voltage vcc5v0-otg-regulator: vcc5v0_otg supplying 0uV | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: vcc5v0_hub: no parameters | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: reg-fixed-voltage vcc5v0-usbhub-regulator: vcc5v0_hub supplying 0uV | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: pcie30_avdd0v9: 900 mV | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: reg-fixed-voltage pcie30-avdd0v9: Looking up vin-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: pcie30_avdd0v9: supplied by vcc3v3_sys | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: reg-fixed-voltage pcie30-avdd0v9: pcie30_avdd0v9 supplying 900000uV | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: pcie30_avdd1v8: 1800 mV | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: reg-fixed-voltage pcie30-avdd1v8: Looking up vin-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: pcie30_avdd1v8: supplied by vcc3v3_sys | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: reg-fixed-voltage pcie30-avdd1v8: pcie30_avdd1v8 supplying 1800000uV | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: vcc3v3_bu: 3300 mV | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: reg-fixed-voltage vcc3v3-bu: Looking up vin-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: vcc3v3_bu: supplied by vcc5v0_sys | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: reg-fixed-voltage vcc3v3-bu: vcc3v3_bu supplying 3300000uV | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: pcie30_3v3: 100 <--> 3300 mV at 3300 mV | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_npu-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_npu-supply property in node /power-management@fdd90000/power-controller failed | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk_iommu fde4b000.iommu: version = 2 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk_iommu fdea0800.iommu: version = 2 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_vpu-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_vpu-supply property in node /power-management@fdd90000/power-controller failed | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk_iommu fded0480.iommu: version = 2 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_rga-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_rga-supply property in node /power-management@fdd90000/power-controller failed | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk_iommu fdee0800.iommu: version = 2 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk_iommu fdef0800.iommu: version = 2 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk_iommu fdf40f00.iommu: version = 2 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_rkvenc-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_rkvenc-supply property in node /power-management@fdd90000/power-controller failed | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk_iommu fdf80800.iommu: version = 2 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_rkvdec-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_rkvdec-supply property in node /power-management@fdd90000/power-controller failed | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk_iommu fdff1a00.iommu: version = 2 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_vi-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_vi-supply property in node /power-management@fdd90000/power-controller failed | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk_iommu fe043e00.iommu: version = 2 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: SCSI subsystem initialized | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: libata version 3.00 loaded. | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: usbcore: registered new interface driver usbfs | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: usbcore: registered new interface driver hub | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: usbcore: registered new device driver usb | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: media: Linux media interface: v0.10 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: videodev: Linux video capture interface: v2.00 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: pps_core: LinuxPPS API ver. 1 registered | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: PTP clock support registered | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: arm-scmi firmware:scmi: SCMI Protocol v2.0 'rockchip:' Firmware version 0x0 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Advanced Linux Sound Architecture Driver Initialized. | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-cpuinfo cpuinfo: SoC : 35682000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-cpuinfo cpuinfo: Serial : 26334c16a41e283c | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: clocksource: Switched to clocksource arch_sys_counter | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: VFS: Disk quotas dquot_6.6.0 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: thermal thermal_zone1: power_allocator: sustainable_power will be estimated | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: NET: Registered protocol family 2 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: tcp_listen_portaddr_hash hash table entries: 4096 (order: 5, 163840 bytes) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: TCP established hash table entries: 65536 (order: 7, 524288 bytes) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: TCP bind hash table entries: 65536 (order: 9, 2097152 bytes) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: TCP: Hash tables configured (established 65536 bind 65536) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: UDP hash table entries: 4096 (order: 6, 393216 bytes) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: UDP-Lite hash table entries: 4096 (order: 6, 393216 bytes) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: NET: Registered protocol family 1 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: RPC: Registered named UNIX socket transport module. | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: RPC: Registered udp transport module. | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: RPC: Registered tcp transport module. | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: PCI: CLS 0 bytes, default 64 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Trying to unpack rootfs image as initramfs... | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Freeing initrd memory: 9048K | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Initialise system trusted keyrings | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: workingset: timestamp_bits=45 max_order=21 bucket_order=0 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: NFS: Registering the id_resolver key type | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Key type id_resolver registered | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Key type id_legacy registered | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: nfs4filelayout_init: NFSv4 File Layout Driver Registering... | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering... | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: ntfs: driver 2.1.32 [Flags: R/W]. | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: NET: Registered protocol family 38 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Key type asymmetric registered | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Asymmetric key parser 'x509' registered | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: io scheduler noop registered | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: io scheduler deadline registered | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: io scheduler cfq registered (default) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: io scheduler mq-deadline registered | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: io scheduler kyber registered | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe8a0000.usb2-phy.0: Looking up phy-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: vcc5v0_host: could not add device link phy-fe8a0000.usb2-phy.0 err -2 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe8a0000.usb2-phy.0: Linked as a consumer to regulator.4 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe8a0000.usb2-phy.1: Looking up phy-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe8a0000.usb2-phy.1: Looking up phy-supply property in node /usb2-phy@fe8a0000/otg-port failed | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe8a0000.usb2-phy.1: Looking up vbus-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe8a0000.usb2-phy.1: Linked as a consumer to regulator.5 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: extcon extcon1: failed to create extcon usb2-phy link | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe8b0000.usb2-phy.2: Looking up phy-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: vcc5v0_host: could not add device link phy-fe8b0000.usb2-phy.2 err -2 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe8b0000.usb2-phy.2: Linked as a consumer to regulator.4 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe8b0000.usb2-phy.3: Looking up phy-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: vcc5v0_host: could not add device link phy-fe8b0000.usb2-phy.3 err -2 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe8b0000.usb2-phy.3: Linked as a consumer to regulator.4 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe8b0000.usb2-phy.3: Looking up vbus-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe8b0000.usb2-phy.3: Looking up vbus-supply property in node /usb2-phy@fe8b0000/otg-port failed | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe8b0000.usb2-phy.3: No vbus specified for otg port | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe850000.video-phy.4: Looking up phy-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe850000.video-phy.4: Looking up phy-supply property in node /video-phy@fe850000 failed | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe820000.phy.5: Looking up phy-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe820000.phy.5: Looking up phy-supply property in node /phy@fe820000 failed | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe830000.phy.6: Looking up phy-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe830000.phy.6: Looking up phy-supply property in node /phy@fe830000 failed | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe840000.phy.7: Looking up phy-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe840000.phy.7: Looking up phy-supply property in node /phy@fe840000 failed | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe8c0000.phy.8: Looking up phy-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: phy phy-fe8c0000.phy.8: Looking up phy-supply property in node /phy@fe8c0000 failed | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: Looking up vpcie3v3-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: Linked as a consumer to regulator.10 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk-pcie 3c0800000.pcie: Looking up vpcie3v3-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: missing legacy IRQ resource | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk-pcie 3c0800000.pcie: Linked as a consumer to regulator.10 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: Missing *config* reg space | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: host bridge /pcie@fe260000 ranges: | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: err 0x300000000..0x3007fffff -> 0x00000000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: IO 0x300800000..0x3008fffff -> 0x00800000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: MEM 0x300900000..0x33fffffff -> 0x00900000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_service mpp-srv: eccf16e83556 author: Finley Xiao 2021-07-05 soc: rockchip: opp_select: Export rockchip_nvmem_cell_read_u8/u16() | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_service mpp-srv: probe start | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk-pcie 3c0800000.pcie: missing legacy IRQ resource | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk-pcie 3c0800000.pcie: Missing *config* reg space | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk-pcie 3c0800000.pcie: host bridge /pcie@fe280000 ranges: | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk-pcie 3c0800000.pcie: err 0x380000000..0x3807fffff -> 0x80000000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk-pcie 3c0800000.pcie: IO 0x380800000..0x3808fffff -> 0x80800000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rk-pcie 3c0800000.pcie: MEM 0x380900000..0x3bfffffff -> 0x80900000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: iommu: Adding device fdf40000.rkvenc to group 5 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_rkvenc fdf40000.rkvenc: Linked as a consumer to fdf40f00.iommu | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_rkvenc fdf40000.rkvenc: probing start | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_rkvenc fdf40000.rkvenc: Looking up venc-supply from device tree | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_rkvenc fdf40000.rkvenc: Looking up venc-supply property in node /rkvenc@fdf40000 failed | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_rkvenc fdf40000.rkvenc: no regulator, devfreq is disabled | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_rkvenc fdf40000.rkvenc: probing finish | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: iommu: Adding device fdea0400.vdpu to group 1 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_vdpu2 fdea0400.vdpu: Linked as a consumer to fdea0800.iommu | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_vdpu2 fdea0400.vdpu: probe device | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_vdpu2 fdea0400.vdpu: probing finish | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: iommu: Adding device fdee0000.vepu to group 3 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_vepu2 fdee0000.vepu: Linked as a consumer to fdee0800.iommu | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_vepu2 fdee0000.vepu: probe device | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_vepu2 fdee0000.vepu: probing finish | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: iommu: Adding device fdef0000.iep to group 4 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp-iep2 fdef0000.iep: Linked as a consumer to fdef0800.iommu | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp-iep2 fdef0000.iep: probe device | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp-iep2 fdef0000.iep: allocate roi buffer failed | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp-iep2 fdef0000.iep: probing finish | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: iommu: Adding device fded0000.jpegd to group 2 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_jpgdec fded0000.jpegd: Linked as a consumer to fded0480.iommu | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_jpgdec fded0000.jpegd: probe device | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_jpgdec fded0000.jpegd: probing finish | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: iommu: Adding device fdf80200.rkvdec to group 6 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_rkvdec2 fdf80200.rkvdec: Linked as a consumer to fdf80800.iommu | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_rkvdec2 fdf80200.rkvdec: probing start | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_rkvdec2 fdf80200.rkvdec: shared_niu_a is not found! | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rkvdec2_init:875: No niu aclk reset resource define | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_rkvdec2 fdf80200.rkvdec: shared_niu_h is not found! | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rkvdec2_init:878: No niu hclk reset resource define | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_rkvdec2 fdf80200.rkvdec: sram_start 0x00000000fdcc0000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_rkvdec2 fdf80200.rkvdec: rcb_iova 0x0000000010000000 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_rkvdec2 fdf80200.rkvdec: sram_size 45056 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_rkvdec2 fdf80200.rkvdec: rcb_size 65536 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_rkvdec2 fdf80200.rkvdec: min_width 512 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_rkvdec2 fdf80200.rkvdec: probing finish | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: mpp_service mpp-srv: probe success | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: dma-pl330 fe530000.dmac: Loaded driver for PL330 DMAC-241330 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: dma-pl330 fe530000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: dma-pl330 fe550000.dmac: Loaded driver for PL330 DMAC-241330 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: dma-pl330 fe550000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-system-monitor rockchip-system-monitor: system monitor probe | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: Serial: 8250/16550 driver, 10 ports, IRQ sharing disabled | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: fe650000.serial: ttyS1 at MMIO 0xfe650000 (irq = 64, base_baud = 1500000) is a 16550A | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: random: fast init done | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: random: crng init done | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: iommu: Adding device fe040000.vop to group 8 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-vop2 fe040000.vop: Linked as a consumer to fe043e00.iommu | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-drm display-subsystem: Linked as a consumer to fe040000.vop | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-drm display-subsystem: Linked as a consumer to fe0a0000.hdmi | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-drm display-subsystem: defer getting devfreq | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp0 assign plane mask: 0x0, primary plane phy id: -1 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp1 assign plane mask: 0x0, primary plane phy id: -1 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp2 assign plane mask: 0x0, primary plane phy id: -1 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: [drm] unsupported AFBC format[3432564e] | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: [drm] failed to init overlay plane Cluster0-win1 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: [drm] failed to init overlay plane Cluster1-win1 | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: rockchip-drm display-subsystem: bound fe040000.vop (ops 0xffff000008da1838) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: dwhdmi-rockchip fe0a0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY) | |
| Apr 01 09:43:04 k3s-rock-3a-1 kernel: dwhdmi-rockchip fe0a0000.hdmi: registered DesignWare HDMI I2C bus driver | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-drm display-subsystem: bound fe0a0000.hdmi (ops 0xffff000008da5868) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [drm] No driver support for vblank timestamp query. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-drm display-subsystem: failed to parse loader memory | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [drm] Cannot find any crtc or sizes | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [drm] Cannot find any crtc or sizes | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [drm] Initialized rockchip 2.0.0 20140818 for display-subsystem on minor 0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_gpu-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-pm-domain fdd90000.power-management:power-controller: Looking up pd_gpu-supply property in node /power-management@fdd90000/power-controller failed | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: Kernel DDK version g2p0-01eac0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: Looking up mali-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: Power management initialization failed error = -517 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: Device initialization Deferred | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cacheinfo: Unable to detect cache hierarchy for CPU 0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: brd: module loaded | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: loop: module loaded | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: zram: Added device: zram0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: lkdtm: No crash points registered, enable through debugfs | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: Loading iSCSI transport class v2.0-870. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: iscsi: registered transport (tcp) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: libphy: Fixed MDIO Bus: probed | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: CAN device driver interface | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet: Looking up phy-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet: Looking up phy-supply property in node /ethernet@fe010000 failed | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet: no regulator found | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet: clock input or output? (output). | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet: TX delay(0x42). | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet: RX delay(0x28). | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet: integrated PHY? (no). | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet: init for RGMII | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet: User ID: 0x30, Synopsys ID: 0x51 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet: DWMAC4/5 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet: DMA HW capability register supported | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet: RX Checksum Offload Engine supported | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet: TX Checksum insertion supported | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet: Wake-Up On Lan supported | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet: TSO supported | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet: Enable RX Mitigation via HW Watchdog Timer | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet: TSO feature enabled | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: libphy: stmmac: probed | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: PPP generic driver version 2.4.2 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: PPP BSD Compression module registered | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: PPP Deflate Compression module registered | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: PPP MPPE Compression module registered | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usbcore: registered new interface driver rndis_wlan | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usbcore: registered new interface driver asix | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usbcore: registered new interface driver cdc_ether | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usbcore: registered new interface driver rndis_host | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usbcore: registered new interface driver cdc_ncm | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ehci-pci: EHCI PCI platform driver | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ehci-platform: EHCI generic platform driver | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ehci-platform fd800000.usb: EHCI Host Controller | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ehci-platform fd800000.usb: new USB bus registered, assigned bus number 1 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ehci-platform fd800000.usb: irq 11, io mem 0xfd800000 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ehci-platform fd800000.usb: USB 2.0 started, EHCI 1.00 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb1: Product: EHCI Host Controller | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb1: Manufacturer: Linux 4.19.193-1001-rockchip-g12d0b2b258a3 ehci_hcd | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb1: SerialNumber: fd800000.usb | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: hub 1-0:1.0: USB hub found | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: hub 1-0:1.0: 1 port detected | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ehci-platform fd880000.usb: EHCI Host Controller | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ehci-platform fd880000.usb: new USB bus registered, assigned bus number 2 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ehci-platform fd880000.usb: irq 13, io mem 0xfd880000 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ehci-platform fd880000.usb: USB 2.0 started, EHCI 1.00 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb2: Product: EHCI Host Controller | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb2: Manufacturer: Linux 4.19.193-1001-rockchip-g12d0b2b258a3 ehci_hcd | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb2: SerialNumber: fd880000.usb | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: hub 2-0:1.0: USB hub found | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: hub 2-0:1.0: 1 port detected | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ohci-platform: OHCI generic platform driver | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ohci-platform fd840000.usb: Generic Platform OHCI controller | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ohci-platform fd840000.usb: new USB bus registered, assigned bus number 3 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ohci-platform fd840000.usb: irq 12, io mem 0xfd840000 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb3: Product: Generic Platform OHCI controller | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb3: Manufacturer: Linux 4.19.193-1001-rockchip-g12d0b2b258a3 ohci_hcd | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb3: SerialNumber: fd840000.usb | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: hub 3-0:1.0: USB hub found | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: hub 3-0:1.0: 1 port detected | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ohci-platform fd8c0000.usb: Generic Platform OHCI controller | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ohci-platform fd8c0000.usb: new USB bus registered, assigned bus number 4 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ohci-platform fd8c0000.usb: irq 14, io mem 0xfd8c0000 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb4: Product: Generic Platform OHCI controller | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb4: Manufacturer: Linux 4.19.193-1001-rockchip-g12d0b2b258a3 ohci_hcd | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb4: SerialNumber: fd8c0000.usb | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: hub 4-0:1.0: USB hub found | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: hub 4-0:1.0: 1 port detected | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usbcore: registered new interface driver usb-storage | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usbcore: registered new interface driver usbtouchscreen | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cyttsp5_loader_init: Parade TTSP FW Loader Driver (Built TTDA.03.08.874312) rc=0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cyttsp5_device_access_init: Parade TTSP Device Access Driver (Built TTDA.03.08.874312) rc=0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: i2c /dev entries driver | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: fan53555-regulator 0-001c: FAN53555 Option[12] Rev[15] Detected! | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vdd_cpu: override max_uV, 1390000 -> 1387500 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vdd_cpu: 712 <--> 1387 mV at 825 mV | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: fan53555-regulator 0-001c: Looking up vin-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vdd_cpu: supplied by vcc5v0_sys | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: chip id: 0x8090 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: No cache defaults, reading back from HW | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: source: on=0x80, off=0x04 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: support dcdc3 fb mode:-22, 63 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: support pmic reset mode:0,0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808-regulator rk808-regulator: there is no dvs0 gpio | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808-regulator rk808-regulator: there is no dvs1 gpio | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vdd_logic: 500 <--> 1350 mV at 900 mV | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: Looking up vcc1-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vdd_logic: supplied by vcc3v3_sys | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vdd_gpu: 500 <--> 1350 mV at 900 mV | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: Looking up vcc2-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vdd_gpu: supplied by vcc3v3_sys | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vcc_ddr: at 500 mV | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: Looking up vcc3-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vcc_ddr: supplied by vcc3v3_sys | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vdd_npu: 500 <--> 1350 mV at 900 mV | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: Looking up vcc4-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vdd_npu: supplied by vcc3v3_sys | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vcc_1v8: 1800 mV | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: Looking up vcc9-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vcc_1v8: supplied by vcc3v3_sys | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vdda0v9_image: 900 mV | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: Looking up vcc5-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vdda0v9_image: supplied by vcc3v3_sys | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vdda_0v9: 900 mV | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: Looking up vcc5-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vdda_0v9: supplied by vcc3v3_sys | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vdda0v9_pmu: 900 mV | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: Looking up vcc5-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vdda0v9_pmu: supplied by vcc3v3_sys | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vccio_acodec: 3300 mV | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: Looking up vcc6-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vccio_acodec: supplied by vcc3v3_sys | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vccio_sd: 1800 <--> 3300 mV at 1800 mV | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: Looking up vcc6-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vccio_sd: supplied by vcc3v3_sys | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vcc3v3_pmu: 3300 mV | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: Looking up vcc6-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vcc3v3_pmu: supplied by vcc3v3_sys | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vcca_1v8: 1800 mV | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: Looking up vcc7-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vcca_1v8: supplied by vcc3v3_sys | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vcca1v8_pmu: 1800 mV | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: Looking up vcc7-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vcca1v8_pmu: supplied by vcc3v3_sys | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vcca1v8_image: 1800 mV | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: Looking up vcc7-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vcca1v8_image: supplied by vcc3v3_sys | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vcc_3v3: no parameters | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: Looking up vcc9-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vcc_3v3: supplied by vcc3v3_sys | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vcc3v3_sd: no parameters | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808 0-0020: Looking up vcc8-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vcc3v3_sd: supplied by vcc3v3_sys | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk817-battery rk817-battery: Failed to find matching dt id | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk817-charger rk817-charger: Failed to find matching dt id | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: input: rk805 pwrkey as /devices/platform/fdd40000.i2c/i2c-0/0-0020/rk805-pwrkey/input/input0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808-rtc rk808-rtc: registered as rtc0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk808-rtc rk808-rtc: setting system clock to 2022-04-01 09:43:01 UTC (1648806181) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: iommu: Adding device fdff0000.rkisp to group 7 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rkisp_hw fdff0000.rkisp: Linked as a consumer to fdff1a00.iommu | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rkisp_hw fdff0000.rkisp: is_thunderboot: 0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rkisp_hw fdff0000.rkisp: max input:0x0@0fps | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rkisp_hw fdff0000.rkisp: can't request region for resource [mem 0xfdff0000-0xfdffffff] | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usbcore: registered new interface driver uvcvideo | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: USB Video Class driver (1.1.1) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: Looking up pmuio1-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: Linked as a consumer to regulator.22 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: pmuio1(3300000 uV) supplied by vcc3v3_pmu | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: Looking up pmuio2-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: pmuio2(3300000 uV) supplied by vcc3v3_pmu | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: Looking up vccio1-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: Linked as a consumer to regulator.20 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: vccio1(3300000 uV) supplied by vccio_acodec | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: Looking up vccio2-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: Looking up vccio2-supply property in node /syscon@fdc20000/io-domains failed | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: Looking up vccio3-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: Linked as a consumer to regulator.21 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: vccio3(1800000 uV) supplied by vccio_sd | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: Looking up vccio4-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: Linked as a consumer to regulator.16 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: vccio4(1800000 uV) supplied by vcc_1v8 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: Looking up vccio5-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: Linked as a consumer to regulator.26 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: vccio5(3300000 uV) supplied by vcc_3v3 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: Looking up vccio6-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: vccio6(1800000 uV) supplied by vcc_1v8 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: Looking up vccio7-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-iodomain fdc20000.syscon:io-domains: vccio7(3300000 uV) supplied by vcc_3v3 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-thermal fe710000.tsadc: tsadc is probed successfully! | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cpu cpu0: leakage=30 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cpu cpu0: Looking up cpu-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cpu cpu0: Linked as a consumer to regulator.11 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cpu cpu0: temp=45555, pvtm=88053 (87923 + 130) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cpu cpu0: Dropping the link to regulator.11 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cpu cpu0: pvtm-volt-sel=1 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cpu cpu0: Looking up cpu-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cpu cpu0: Linked as a consumer to regulator.11 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cpu cpu0: Dropping the link to regulator.11 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cpu cpu0: Looking up cpu-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cpu cpu0: Linked as a consumer to regulator.11 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cpu cpu0: avs=0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: energy_model: pd0: hertz/watts ratio non-monotonically decreasing: em_cap_state 2 >= em_cap_state1 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: energy_model: Created perf domain 0-3 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cpu cpu0: l=0 h=2147483647 hyst=5000 l_limit=0 h_limit=0 h_table=0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: sdhci: Secure Digital Host Controller Interface driver | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: sdhci: Copyright(c) Pierre Ossman | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: Synopsys Designware Multimedia Card Interface Driver | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe000000.dwmmc: IDMAC supports 32-bit address mode. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe000000.dwmmc: Using internal DMA controller. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe000000.dwmmc: Version ID is 270a | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe000000.dwmmc: DW MMC controller at irq 41,32 bit host data width,256 deep fifo | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe000000.dwmmc: Looking up vmmc-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe000000.dwmmc: Looking up vmmc-supply property in node /dwmmc@fe000000 failed | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe000000.dwmmc: Looking up vqmmc-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe000000.dwmmc: Looking up vqmmc-supply property in node /dwmmc@fe000000 failed | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe000000.dwmmc: allocated mmc-pwrseq | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmc_host mmc3: card is non-removable. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb 1-1: new high-speed USB device number 2 using ehci-platform | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmc_host mmc3: Bus speed (slot 0) = 375000Hz (slot req 400000Hz, actual 375000HZ div = 0) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe2b0000.dwmmc: IDMAC supports 32-bit address mode. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe2b0000.dwmmc: Using internal DMA controller. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe2b0000.dwmmc: Version ID is 270a | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe2b0000.dwmmc: DW MMC controller at irq 53,32 bit host data width,256 deep fifo | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe2b0000.dwmmc: Looking up vmmc-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe2b0000.dwmmc: Linked as a consumer to regulator.27 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe2b0000.dwmmc: Looking up vqmmc-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe2b0000.dwmmc: Linked as a consumer to regulator.21 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vccio_sd: ramp_delay not set | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmc3 mmc_send_io_op_cond err: -110 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmc_host mmc1: Bus speed (slot 0) = 375000Hz (slot req 400000Hz, actual 375000HZ div = 0) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmc_host mmc3: Bus speed (slot 0) = 375000Hz (slot req 300000Hz, actual 187500HZ div = 1) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: sdhci-pltfm: SDHCI platform and OF driver helper | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: sdhci-dwcmshc fe310000.sdhci: Looking up vmmc-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: sdhci-dwcmshc fe310000.sdhci: Looking up vmmc-supply property in node /sdhci@fe310000 failed | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: sdhci-dwcmshc fe310000.sdhci: Looking up vqmmc-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: sdhci-dwcmshc fe310000.sdhci: Looking up vqmmc-supply property in node /sdhci@fe310000 failed | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmc0: Unknown controller version (5). You may experience problems. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmc_host mmc3: Bus speed (slot 0) = 375000Hz (slot req 375000Hz, actual 375000HZ div = 0) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmc3 mmc_send_io_op_cond err: -110 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vccio_sd: ramp_delay not set | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmc0: SDHCI controller on fe310000.sdhci [fe310000.sdhci] using ADMA | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ledtrig-cpu: registered to indicate activity on CPUs | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: hidraw: raw HID events driver (C) Jiri Kosina | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usbcore: registered new interface driver usbhid | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usbhid: USB HID core driver | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip,bus bus-npu: Looking up bus-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip,bus bus-npu: Linked as a consumer to regulator.12 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip,bus bus-npu: Failed to get leakage | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip,bus bus-npu: pvtm = 88053, form pvtm_value | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip,bus bus-npu: pvtm-volt-sel=1 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip,bus bus-npu: avs=0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-saradc fe720000.saradc: Looking up vref-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-saradc fe720000.saradc: Linked as a consumer to regulator.23 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmc_host mmc3: Bus speed (slot 0) = 375000Hz (slot req 200000Hz, actual 187500HZ div = 1) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: optee: probing for conduit method from DT. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: optee: api uid mismatch | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rksfc_base v1.1 2016-01-08 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rksfc fe300000.sfc: rksfc_probe clk rate = 99000000 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rkflash_dev_init enter | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: sfc nor id: c2 25 38 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rkflash[1] init success | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: sfc_nor_mtd_init register mtd succuss | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rkflash_dev_init device register as mtd dev, ret= 0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usbcore: registered new interface driver snd-usb-audio | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmc_host mmc1: Bus speed (slot 0) = 148500000Hz (slot req 150000000Hz, actual 148500000HZ div = 0) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk817-codec rk817-codec: DMA mask not set | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: Initializing XFRM netlink socket | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: NET: Registered protocol family 17 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: can: controller area network core (rev 20170425 abi 9) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: NET: Registered protocol family 29 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [BT_RFKILL]: Enter rfkill_rk_init | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [WLAN_RFKILL]: Enter rfkill_wlan_init | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [WLAN_RFKILL]: Enter rfkill_wlan_probe | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi_chip_type = ap6256 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [WLAN_RFKILL]: wlan_platdata_parse_dt: enable wifi power control. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi power controled by gpio. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [WLAN_RFKILL]: wlan_platdata_parse_dt: WIFI,host_wake_irq = 125, flags = 0. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [WLAN_RFKILL]: rfkill_wlan_probe: init gpio | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [WLAN_RFKILL]: rfkill_set_wifi_bt_power: 1 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [WLAN_RFKILL]: Exit rfkill_wlan_probe | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: uart_rts_gpios = 73. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,reset_gpio = 138. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_gpio = 141. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_host_irq = 140. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [BT_RFKILL]: Request irq for bt wakeup host | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [BT_RFKILL]: ** disable irq | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [BT_RFKILL]: bt_default device registered. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: Key type dns_resolver registered | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: flash vendor_init_thread! | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: flash vendor storage:20170308 ret = -1 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: registered taskstats version 1 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: Loading compiled-in X.509 certificates | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pstore: Using compression: deflate | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rga2: Driver loaded successfully ver:3.2.63318 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rga2: Module initialized. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmc_host mmc3: Bus speed (slot 0) = 375000Hz (slot req 375000Hz, actual 375000HZ div = 0) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwmmc_rockchip fe2b0000.dwmmc: Successfully tuned phase to 253 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmc1: new ultra high speed SDR104 SDHC card at address 59b4 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmcblk1: mmc1:59b4 SDU1 29.5 GiB | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmcblk1: p1 p2 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmc3 mmc_send_io_op_cond err: -110 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmc_host mmc3: Bus speed (slot 0) = 375000Hz (slot req 100000Hz, actual 93750HZ div = 2) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: Kernel DDK version g2p0-01eac0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: Looking up mali-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: Linked as a consumer to regulator.13 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: Looking up shadercores-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: Looking up shadercores-supply property in node /gpu@fde60000 failed | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: Looking up mali-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vdd_gpu: could not add device link fde60000.gpu err -17 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vdd_gpu: Failed to create debugfs directory | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: Looking up shadercores-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: Looking up shadercores-supply property in node /gpu@fde60000 failed | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: dev_pm_opp_set_regulators: no regulator (shadercores) found: -19 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: leakage=8 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: avs=0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: W : [File] : drivers/gpu/arm/bifrost/platform/rk/mali_kbase_config_rk.c; [Line] : 112; [Func] : kbase_platform_rk_init(); power-off-delay-ms not available. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: GPU identified as 0x2 arch 7.4.0 r1p0 status 0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: No memory group manager is configured | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: l=-2147483648 h=2147483647 hyst=0 l_limit=0 h_limit=0 h_table=0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mali fde60000.gpu: Probed as mali0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: adc_keys adc-keys: keymap is missing | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: adc_keys: probe of adc-keys failed with error -22 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-dmc dmc: Looking up center-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-dmc dmc: Linked as a consumer to regulator.12 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-dmc dmc: leakage=55 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-dmc dmc: leakage-volt-sel=0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-dmc dmc: avs=0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-dmc dmc: current ATF version 0x101 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-dmc dmc: normal_rate = 780000000 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-dmc dmc: reboot_rate = 1056000000 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-dmc dmc: suspend_rate = 324000000 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-dmc dmc: video_4k_rate = 780000000 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-dmc dmc: video_4k_10b_rate = 780000000 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-dmc dmc: boost_rate = 1056000000 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-dmc dmc: fixed_rate(isp|cif0|cif1|dualview) = 1056000000 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-dmc dmc: performance_rate = 1056000000 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-dmc dmc: failed to get vop pn to msch rl | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-dmc dmc: l=0 h=2147483647 hyst=5000 l_limit=0 h_limit=0 h_table=0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-dmc dmc: could not find power_model node | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: asoc-simple-card hdmi-sound: i2s-hifi <-> fe400000.i2s mapping ok | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: asoc-simple-card rk809-sound: rk817-hifi <-> fe410000.i2s mapping ok | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb 1-1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb 1-1: Product: USB 2.0 Hub | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmc_host mmc3: Bus speed (slot 0) = 375000Hz (slot req 375000Hz, actual 375000HZ div = 0) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: hub 1-1:1.0: USB hub found | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: hub 1-1:1.0: 4 ports detected | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip_headset rk-headset: Can not read property hook_gpio | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip_headset rk-headset: headset have hook adc mode | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: input: rk-headset as /devices/platform/rk-headset/input/input1 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: iommu: Adding device fde40000.npu to group 0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: RKNPU fde40000.npu: Linked as a consumer to fde4b000.iommu | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: RKNPU fde40000.npu: RKNPU: rknpu iommu is enabled, using iommu mode | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: RKNPU fde40000.npu: Looking up rknpu-supply from device tree | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: RKNPU fde40000.npu: Linked as a consumer to regulator.15 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: RKNPU fde40000.npu: can't request region for resource [mem 0xfde40000-0xfde4ffff] | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: [drm] Initialized rknpu 0.4.2 20210701 for fde40000.npu on minor 1 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: RKNPU fde40000.npu: leakage=4 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: RKNPU fde40000.npu: avs=0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: RKNPU fde40000.npu: l=0 h=2147483647 hyst=5000 l_limit=0 h_limit=0 h_table=0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: mmc3 mmc_send_io_op_cond err: -110 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rockchip-pm rockchip-suspend: not set pwm-regulator-config | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: I : [File] : drivers/gpu/arm/mali400/mali/linux/mali_kernel_linux.c; [Line] : 413; [Func] : mali_module_init(); svn_rev_string_from_arm of this mali_ko is '', rk_ko_ver is '5', built at '13:27:00', on 'Mar 31 2022'. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: Mali: | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: Mali device driver loaded | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: ALSA device list: | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: #0: rockchip,hdmi | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: #1: rockchip,rk809-codec | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: Freeing unused kernel memory: 1536K | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: cfg80211: failed to load regulatory.db | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: Run /init as init process | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: devfreq fde60000.gpu: Couldn't update frequency transition information. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: PCIe Linking... LTSSM is 0x0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk-pcie 3c0800000.pcie: PCIe Linking... LTSSM is 0x3 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwc3 fcc00000.dwc3: Failed to get clk 'ref': -2 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: dwc3 fd000000.dwc3: Failed to get clk 'ref': -2 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: xhci-hcd xhci-hcd.4.auto: xHCI Host Controller | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: xhci-hcd xhci-hcd.4.auto: new USB bus registered, assigned bus number 5 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: xhci-hcd xhci-hcd.4.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0000011002010010 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: xhci-hcd xhci-hcd.4.auto: irq 104, io mem 0xfd000000 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb5: Product: xHCI Host Controller | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb5: Manufacturer: Linux 4.19.193-1001-rockchip-g12d0b2b258a3 xhci-hcd | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb5: SerialNumber: xhci-hcd.4.auto | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: hub 5-0:1.0: USB hub found | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: hub 5-0:1.0: 1 port detected | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: xhci-hcd xhci-hcd.4.auto: xHCI Host Controller | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: xhci-hcd xhci-hcd.4.auto: new USB bus registered, assigned bus number 6 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: xhci-hcd xhci-hcd.4.auto: Host supports USB 3.0 SuperSpeed | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb6: We don't know the algorithms for LPM for this host, disabling LPM. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb6: Product: xHCI Host Controller | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb6: Manufacturer: Linux 4.19.193-1001-rockchip-g12d0b2b258a3 xhci-hcd | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: usb usb6: SerialNumber: xhci-hcd.4.auto | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: hub 6-0:1.0: USB hub found | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: hub 6-0:1.0: 1 port detected | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: PCIe Linking... LTSSM is 0x0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk-pcie 3c0800000.pcie: PCIe Link up, LTSSM is 0x30011 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk-pcie 3c0800000.pcie: PCI host bridge to bus 0002:20 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci_bus 0002:20: root bus resource [bus 20-2f] | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci_bus 0002:20: root bus resource [??? 0x380000000-0x3807fffff flags 0x0] (bus address [0x80000000-0x807fffff]) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci_bus 0002:20: root bus resource [io 0x100000-0x1fffff] (bus address [0x80800000-0x808fffff]) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci_bus 0002:20: root bus resource [mem 0x380900000-0x3bfffffff] (bus address [0x80900000-0xbfffffff]) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci 0002:20:00.0: [1d87:3566] type 01 class 0x060400 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci 0002:20:00.0: reg 0x10: [mem 0x00000000-0x3fffffff 64bit] | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci 0002:20:00.0: reg 0x38: [mem 0x00000000-0x0000ffff pref] | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci 0002:20:00.0: supports D1 D2 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci 0002:20:00.0: PME# supported from D0 D1 D3hot | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci 0002:20:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci 0002:21:00.0: [c0a9:540a] type 00 class 0x010802 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci 0002:21:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit] | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci 0002:21:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s x2 link at 0002:20:00.0 (capable of 31.504 Gb/s with 8 GT/s x4 link) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci_bus 0002:21: busn_res: [bus 21-2f] end is updated to 21 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci 0002:20:00.0: BAR 0: no space for [mem size 0x40000000 64bit] | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci 0002:20:00.0: BAR 0: failed to assign [mem size 0x40000000 64bit] | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci 0002:20:00.0: BAR 8: assigned [mem 0x380900000-0x3809fffff] | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci 0002:20:00.0: BAR 6: assigned [mem 0x380a00000-0x380a0ffff pref] | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci 0002:21:00.0: BAR 0: assigned [mem 0x380900000-0x380903fff 64bit] | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci 0002:20:00.0: PCI bridge to [bus 21] | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pci 0002:20:00.0: bridge window [mem 0x380900000-0x3809fffff] | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pcieport 0002:20:00.0: Signaling PME with IRQ 114 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: pcieport 0002:20:00.0: AER enabled with IRQ 115 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: nvme nvme0: pci function 0002:21:00.0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: nvme 0002:21:00.0: enabling device (0000 -> 0002) | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: nvme nvme0: missing or invalid SUBNQN field. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: NET: Registered protocol family 10 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: Segment Routing with IPv6 | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: nvme nvme0: allocated 128 MiB host memory buffer. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: systemd 245.4-4ubuntu3.15 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid) | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Detected architecture arm64. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Set hostname to <k3s-rock-3a-1>. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: system-modprobe.slice: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: (This warning is only shown for the first unit using IP firewalling.) | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Created slice system-modprobe.slice. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Created slice system-systemd\x2dfsck.slice. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Created slice User and Session Slice. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Started ntp-systemd-netif.path. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Started Dispatch Password Requests to Console Directory Watch. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Started Forward Password Requests to Wall Directory Watch. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Reached target Local Encrypted Volumes. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Reached target Slices. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Reached target Swap. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Listening on RPCbind Server Activation Socket. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Listening on fsck to fsckd communication Socket. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Listening on initctl Compatibility Named Pipe. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: phy phy-fe8a0000.usb2-phy.1: charger = USB_DCP_CHARGER | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in Journal Audit Socket being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Listening on Journal Socket (/dev/log). | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Listening on Journal Socket. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Listening on udev Control Socket. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Listening on udev Kernel Socket. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in Huge Pages File System being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Mounting POSIX Message Queue File System... | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: PCIe Linking... LTSSM is 0x0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Mounting NFSD configuration filesystem... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Mounting RPC Pipe File System... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Mounting Kernel Debug File System... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Mounting Kernel Trace File System... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Starting Journal Service... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in Kernel Module supporting RPCSEC_GSS being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Starting Restore / save the current clock... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Starting Set the console keyboard layout... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Starting Create list of static device nodes for the current kernel... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in Load Kernel Module drm being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Started Nameserver information manager. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Reached target Network (Pre). | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de). | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in File System Check on Root Device being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Starting Load Kernel Modules... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Starting Remount Root and Kernel File Systems... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Starting udev Coldplug all Devices... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Mounted POSIX Message Queue File System. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Mounted NFSD configuration filesystem. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Mounted RPC Pipe File System. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Mounted Kernel Debug File System. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Mounted Kernel Trace File System. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Finished Restore / save the current clock. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Finished Create list of static device nodes for the current kernel. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: EXT4-fs (mmcblk1p2): re-mounted. Opts: (null) | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Finished Load Kernel Modules. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Finished Remount Root and Kernel File Systems. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in FUSE Control File System being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Mounting Kernel Configuration File System... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Starting pNFS block layout mapping daemon... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Starting Apply Kernel Variables... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Starting Create System Users... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Mounted Kernel Configuration File System. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Started pNFS block layout mapping daemon. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Finished Apply Kernel Variables. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Finished Create System Users. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Starting Create Static Device Nodes in /dev... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Finished Set the console keyboard layout. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Finished Create Static Device Nodes in /dev. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Reached target Local File Systems (Pre). | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Set up automount boot.automount. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Starting udev Kernel Device Manager... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Started udev Kernel Device Manager. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Finished udev Coldplug all Devices. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Starting Helper to synchronize boot up for ifupdown... | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: vendor storage:20190527 ret = -1 | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Finished Helper to synchronize boot up for ifupdown. | |
| Apr 01 09:43:05 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: PCIe Linking... LTSSM is 0x0 | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Found device CT1000P2SSD8. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Starting File System Check on /dev/disk/by-uuid/12475a6b-a017-4b86-88c2-cac3c5d8fbe8... | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Started File System Check Daemon to report status. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in Journal Audit Socket being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in Huge Pages File System being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in FUSE Control File System being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in File System Check on Root Device being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in Journal Audit Socket being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in Huge Pages File System being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in FUSE Control File System being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in File System Check on Root Device being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. | |
| Apr 01 09:43:05 k3s-rock-3a-1 systemd[1]: Started Journal Service. | |
| Apr 01 09:43:09 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: PCIe Linking... LTSSM is 0x0 | |
| Apr 01 09:43:09 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: PCIe Linking... LTSSM is 0x0 | |
| Apr 01 09:43:09 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: PCIe Linking... LTSSM is 0x0 | |
| Apr 01 09:43:09 k3s-rock-3a-1 kernel: EXT4-fs (nvme0n1): mounted filesystem with ordered data mode. Opts: (null) | |
| Apr 01 09:43:09 k3s-rock-3a-1 kernel: [BT_RFKILL]: bt shut off power | |
| Apr 01 09:43:09 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: PCIe Linking... LTSSM is 0x0 | |
| Apr 01 09:43:10 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: PCIe Linking... LTSSM is 0x0 | |
| Apr 01 09:43:10 k3s-rock-3a-1 kernel: 8021q: 802.1Q VLAN Support v1.8 | |
| Apr 01 09:43:10 k3s-rock-3a-1 kernel: RTL8211F Gigabit Ethernet stmmac-1:00: attached PHY driver [RTL8211F Gigabit Ethernet] (mii_bus:phy_addr=stmmac-1:00, irq=POLL) | |
| Apr 01 09:43:10 k3s-rock-3a-1 kernel: dwmac4: Master AXI performs any burst length | |
| Apr 01 09:43:10 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet eth0: No Safety Features support found | |
| Apr 01 09:43:10 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet eth0: IEEE 1588-2008 Advanced Timestamp supported | |
| Apr 01 09:43:10 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet eth0: registered PTP clock | |
| Apr 01 09:43:10 k3s-rock-3a-1 kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready | |
| Apr 01 09:43:11 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: PCIe Linking... LTSSM is 0x0 | |
| Apr 01 09:43:11 k3s-rock-3a-1 kernel: NFSD: starting 90-second grace period (net f0000049) | |
| Apr 01 09:43:12 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: PCIe Link Fail | |
| Apr 01 09:43:12 k3s-rock-3a-1 kernel: rk-pcie 3c0000000.pcie: failed to initialize host | |
| Apr 01 09:43:12 k3s-rock-3a-1 kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready | |
| Apr 01 09:43:15 k3s-rock-3a-1 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready | |
| Apr 01 09:43:15 k3s-rock-3a-1 kernel: rk_gmac-dwmac fe010000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx | |
| Apr 01 09:43:15 k3s-rock-3a-1 kernel: capability: warning: `zerotier-one' uses 32-bit capabilities (legacy support in use) | |
| Apr 01 09:43:15 k3s-rock-3a-1 kernel: tun: Universal TUN/TAP device driver, 1.6 | |
| Apr 01 09:43:23 k3s-rock-3a-1 kernel: IPVS: Registered protocols () | |
| Apr 01 09:43:23 k3s-rock-3a-1 kernel: IPVS: Connection hash table configured (size=4096, memory=64Kbytes) | |
| Apr 01 09:43:23 k3s-rock-3a-1 kernel: IPVS: ipvs loaded. | |
| Apr 01 09:43:23 k3s-rock-3a-1 kernel: IPVS: [rr] scheduler registered. | |
| Apr 01 09:43:23 k3s-rock-3a-1 kernel: IPVS: [wrr] scheduler registered. | |
| Apr 01 09:43:23 k3s-rock-3a-1 kernel: IPVS: [sh] scheduler registered. | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: nvme 0002:21:00.0: enabling device (0000 -> 0002) | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: nvme nvme0: Removing after probe failure status: -19 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: print_req_error: I/O error, dev nvme0n1, sector 243270592 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: print_req_error: I/O error, dev nvme0n1, sector 239827040 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: print_req_error: I/O error, dev nvme0n1, sector 974561448 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: EXT4-fs warning (device nvme0n1): ext4_end_bio:309: I/O error 10 writing to inode 7471614 (offset 0 size 4096 starting block 29978381) | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on device nvme0n1, logical block 29978380 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on dev nvme0n1, logical block 30408824, lost async page write | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: print_req_error: I/O error, dev nvme0n1, sector 239827032 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: print_req_error: I/O error, dev nvme0n1, sector 243270552 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on dev nvme0n1, logical block 30408819, lost async page write | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: EXT4-fs warning (device nvme0n1): ext4_end_bio:309: I/O error 10 writing to inode 7471613 (offset 0 size 4096 starting block 29978380) | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: print_req_error: I/O error, dev nvme0n1, sector 239143856 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on device nvme0n1, logical block 29978379 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on dev nvme0n1, logical block 29892982, lost async page write | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: print_req_error: I/O error, dev nvme0n1, sector 239827024 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: print_req_error: I/O error, dev nvme0n1, sector 239486320 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: print_req_error: I/O error, dev nvme0n1, sector 239141872 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on dev nvme0n1, logical block 29892734, lost async page write | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: EXT4-fs warning (device nvme0n1): ext4_end_bio:309: I/O error 10 writing to inode 7471127 (offset 0 size 4096 starting block 29978379) | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on device nvme0n1, logical block 29978378 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: EXT4-fs warning (device nvme0n1): ext4_end_bio:309: I/O error 10 writing to inode 7471617 (offset 0 size 4096 starting block 29935791) | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: print_req_error: I/O error, dev nvme0n1, sector 239078600 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on device nvme0n1, logical block 29935790 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on dev nvme0n1, logical block 29884825, lost async page write | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: EXT4-fs warning (device nvme0n1): ext4_end_bio:309: I/O error 10 writing to inode 7471616 (offset 0 size 4096 starting block 29935790) | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on device nvme0n1, logical block 29935789 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on dev nvme0n1, logical block 29884764, lost async page write | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: EXT4-fs warning (device nvme0n1): ext4_end_bio:309: I/O error 10 writing to inode 7471615 (offset 0 size 4096 starting block 29935789) | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on device nvme0n1, logical block 29935788 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on dev nvme0n1, logical block 29884545, lost async page write | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on dev nvme0n1, logical block 29884483, lost async page write | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on dev nvme0n1, logical block 29884481, lost async page write | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on dev nvme0n1, logical block 23, lost async page write | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: EXT4-fs warning (device nvme0n1): ext4_end_bio:309: I/O error 10 writing to inode 7471620 (offset 0 size 4096 starting block 30471670) | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on device nvme0n1, logical block 30471669 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: EXT4-fs warning (device nvme0n1): ext4_end_bio:309: I/O error 10 writing to inode 7471619 (offset 0 size 4096 starting block 30471669) | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on device nvme0n1, logical block 30471668 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: EXT4-fs warning (device nvme0n1): ext4_end_bio:309: I/O error 10 writing to inode 7471618 (offset 0 size 4096 starting block 30471668) | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Buffer I/O error on device nvme0n1, logical block 30471667 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: JBD2: Detected IO errors while flushing file data on nvme0n1-8 | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: Aborting journal on device nvme0n1-8. | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: JBD2: Error -5 detected when updating journal superblock for nvme0n1-8. | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: EXT4-fs (nvme0n1): I/O error while writing superblock | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): ext4_journal_check_start:61: Detected aborted journal | |
| Apr 01 12:22:43 k3s-rock-3a-1 kernel: EXT4-fs (nvme0n1): Remounting filesystem read-only | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: EXT4-fs (nvme0n1): I/O error while writing superblock | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: JBD2: Error while async write back metadata bh 16. | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: JBD2: Error while async write back metadata bh 17. | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: JBD2: Error while async write back metadata bh 18. | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: JBD2: Error while async write back metadata bh 19. | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: JBD2: Error while async write back metadata bh 21. | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: JBD2: Error while async write back metadata bh 23. | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: JBD2: Error while async write back metadata bh 24. | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: JBD2: Error while async write back metadata bh 29884481. | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: JBD2: Error while async write back metadata bh 29884483. | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: JBD2: Error while async write back metadata bh 29884545. | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: JBD2: Error while async write back metadata bh 29884764. | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: JBD2: Error while async write back metadata bh 29884825. | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: JBD2: Error while async write back metadata bh 29892734. | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: JBD2: Error while async write back metadata bh 29892982. | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: JBD2: Error while async write back metadata bh 30408819. | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: JBD2: Error while async write back metadata bh 30408824. | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: VFS: busy inodes on changed media or resized disk nvme0n1 | |
| Apr 01 12:22:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #6160385: comm systemd-random-: reading directory lblock 0 | |
| Apr 01 12:22:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:22:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:22:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:22:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:23:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm NetworkManager: reading directory lblock 0 | |
| Apr 01 12:23:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:23:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:23:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:23:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:23:41 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:23:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:23:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:23:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:24:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:24:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:24:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:24:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:24:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:24:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:24:44 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 12:24:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:24:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:24:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:25:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:25:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:25:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:25:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:25:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:25:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:25:52 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:25:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:25:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:26:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:26:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:26:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:26:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:26:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:26:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:26:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:26:55 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 12:26:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:26:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:27:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:27:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:27:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:27:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:27:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:27:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:27:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:27:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:27:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:28:04 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 12:28:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:28:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm NetworkManager: reading directory lblock 0 | |
| Apr 01 12:28:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:28:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:28:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:28:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:28:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:28:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:29:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:29:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:29:07 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 12:29:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:29:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:29:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:29:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:29:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:29:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:29:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:29:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:30:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:30:10 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:30:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:30:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:30:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:30:31 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:30:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:30:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:30:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:30:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:31:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:31:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:31:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:31:18 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 12:31:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:31:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:31:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:31:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:31:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:31:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:32:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:32:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:32:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:32:21 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:32:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:32:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:32:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:32:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:32:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:33:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:33:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm NetworkManager: reading directory lblock 0 | |
| Apr 01 12:33:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:33:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:33:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:33:29 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:33:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:33:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:33:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:33:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:34:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:34:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:34:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:34:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:34:32 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:34:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:34:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:34:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:34:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:35:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:35:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:35:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:35:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:35:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:35:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:35:35 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 12:35:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:35:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:35:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:35:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:36:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:36:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:36:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:36:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:36:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:36:43 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:36:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:36:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:36:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:37:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:37:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:37:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:37:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:37:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:37:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:37:46 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 12:37:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:37:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:37:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:38:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:38:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm NetworkManager: reading directory lblock 0 | |
| Apr 01 12:38:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:38:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:38:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:38:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:38:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:38:54 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:38:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:38:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:39:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:39:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:39:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:39:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:39:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:39:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:39:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:39:57 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 12:39:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:39:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:40:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:40:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:40:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:40:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:40:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:40:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:40:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:41:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:41:00 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:41:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:41:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:41:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:41:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:41:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:41:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:41:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:42:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:42:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:42:08 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 12:42:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:42:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:42:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:42:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:42:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:42:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:42:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:43:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:43:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:43:11 k3s-rock-3a-1 kernel: EXT4-fs error: 4 callbacks suppressed | |
| Apr 01 12:43:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm ntpd: reading directory lblock 0 | |
| Apr 01 12:43:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:43:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:43:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:43:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:43:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:43:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:43:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:44:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:44:04 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:44:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:44:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:44:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:44:20 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 12:44:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:44:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:44:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:44:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:44:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:44:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:45:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:45:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:45:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:45:23 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:45:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:45:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:45:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:45:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:45:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:45:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:46:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:46:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:46:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:46:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:46:26 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 12:46:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:46:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:46:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:46:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:46:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:47:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:47:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:47:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:47:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:47:34 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:47:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:47:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:47:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:47:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:48:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:48:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm NetworkManager: reading directory lblock 0 | |
| Apr 01 12:48:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:48:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:48:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:48:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:48:37 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 12:48:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:48:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:48:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:48:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:49:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:49:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:49:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:49:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:49:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:49:45 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:49:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:49:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:49:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:50:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:50:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:50:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:50:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:50:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:50:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:50:48 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 12:50:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:50:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:50:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:51:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:51:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:51:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:51:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:51:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:51:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:51:51 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:51:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:51:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:52:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:52:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:52:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:52:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:52:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:52:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:52:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:52:59 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 12:52:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:52:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:53:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm NetworkManager: reading directory lblock 0 | |
| Apr 01 12:53:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:53:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:53:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:53:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:53:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:53:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:53:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:54:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:54:02 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:54:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:54:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:54:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:54:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:54:34 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:54:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:54:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:54:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:54:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:55:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:55:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:55:11 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 12:55:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:55:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:55:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:55:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:55:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:55:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:55:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:56:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:56:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:56:14 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:56:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:56:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:56:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:56:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:56:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:56:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:57:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:57:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:57:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:57:17 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 12:57:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:57:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:57:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:57:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:57:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:57:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:58:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm NetworkManager: reading directory lblock 0 | |
| Apr 01 12:58:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:58:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:58:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:58:25 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 12:58:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:58:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:58:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:58:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:58:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:59:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:59:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:59:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:59:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:59:28 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 12:59:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:59:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:59:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 12:59:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 12:59:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:00:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:00:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:00:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:00:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:00:36 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 13:00:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:00:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:00:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:00:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:01:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:01:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:01:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:01:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:01:34 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 13:01:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:01:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:01:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:01:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:02:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:02:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:02:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:02:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:02:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:02:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:02:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:02:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:02:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:42 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 13:02:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:02:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:02:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:03:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm NetworkManager: reading directory lblock 0 | |
| Apr 01 13:03:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:03:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:03:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:03:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:03:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:03:45 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 13:03:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:03:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:03:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:04:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:04:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:04:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:04:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:04:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:04:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:04:48 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 13:04:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:04:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:04:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:05:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:05:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:05:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:05:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:05:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:05:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:05:56 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 13:05:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:05:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:06:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:06:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:06:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:06:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:06:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:06:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:06:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:06:59 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 13:06:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:06:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:07:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:07:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:07:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:07:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:07:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:07:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:07:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:08:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:08:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:08:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:08:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:08:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:08 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 13:08:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm NetworkManager: reading directory lblock 0 | |
| Apr 01 13:08:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:08:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:08:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:08:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:08:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:08:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:08:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:09:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:09:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:09:11 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 13:09:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:09:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:09:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:09:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:09:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:09:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:09:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:10:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:10:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:10:14 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 13:10:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:10:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:10:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:10:35 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 13:10:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:10:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:10:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:10:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:11:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:11:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:11:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:11:22 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 13:11:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:11:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:11:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:11:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:11:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:11:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:12:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:12:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:12:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:12:25 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 13:12:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:12:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:12:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:12:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:12:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:13:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm NetworkManager: reading directory lblock 0 | |
| Apr 01 13:13:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:13:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:13:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:13:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:13:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:13:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:13:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:33 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 13:13:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:13:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:13:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:13:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:14:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:14:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:14:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:14:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:14:36 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 13:14:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:14:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:52 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:14:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:14:57 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:15:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:15:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:18 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:15:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:15:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:34 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:15:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:15:39 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 13:15:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:15:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:15:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:15:55 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:16:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:16:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:16 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:16:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:16:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:37 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:42 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:16:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:16:47 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 13:16:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:47 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:16:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:16:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:17:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:08 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:17:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:19 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:17:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:24 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:29 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:17:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:40 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:17:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:45 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:17:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:17:50 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 13:17:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:50 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:17:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:17:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:01 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:18:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:06 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm NetworkManager: reading directory lblock 0 | |
| Apr 01 13:18:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:11 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:18:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:18:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:22 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:18:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:27 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:32 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:18:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:18:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:48 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:18:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:18:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:18:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:18:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:18:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:59 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 13:18:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:18:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:19:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:04 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:09 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:19:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:14 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:19:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:25 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:30 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:19:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:35 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:41 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:19:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:46 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:51 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:19:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:56 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:19:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:19:58 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:20:02 k3s-rock-3a-1 kernel: EXT4-fs error: 2 callbacks suppressed | |
| Apr 01 13:20:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:02 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:20:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:07 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:12 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:20:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:17 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:20:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:28 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:20:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:38 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:39 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:43 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:20:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:44 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:49 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:53 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:20:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:54 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:20:59 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:00 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:21:03 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:21:05 k3s-rock-3a-1 kernel: EXT4-fs error: 3 callbacks suppressed | |
| Apr 01 13:21:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:05 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:10 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:13 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:21:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:15 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:20 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:21 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:23 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:21:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:26 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:31 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:33 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm zerotier-one: reading directory lblock 0 | |
| Apr 01 13:21:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k3s: reading directory lblock 0 | |
| Apr 01 13:21:36 k3s-rock-3a-1 kernel: EXT4-fs error (device nvme0n1): __ext4_find_entry:1609: inode #2: comm k |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment