OCP主机的根目录最近一直被打满，但是拍查不到什么原因，看不懂message里的报错日志。每次都是被message里的日志刷满了空间
日志内容主要是这些：
Jun 30 23:33:27 txcdb174 kernel: [3648710.985334] WARNING: CPU: 62 PID: 2473652 at fs/open.c:1194 filp_close+0xbb/0xf0
Jun 30 23:33:27 txcdb174 kernel: [3648710.985335] Modules linked in: udp_diag xt_nat veth binfmt_misc tcp_diag inet_diag ipt_MASQUERADE nf_conntrack_netlink nfnetlink iptable_nat nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter bridge stp llc overlay aufs rfkill sunrpc vfat fat crct10dif_pclmul joydev sg i2c_piix4 virtio_balloon crc32_pclmul psmouse ghash_clmulni_intel pcspkr ip_tables xfs libcrc32c cirrus drm_kms_helper syscopyarea sysfillrect sr_mod sysimgblt cdrom fb_sys_fops virtio_net ttm ata_generic ata_piix crc32c_intel net_failover virtio_console virtio_blk drm failover serio_raw libata floppy dm_mirror dm_region_hash dm_log dm_mod
Jun 30 23:33:27 txcdb174 kernel: [3648710.985354] CPU: 62 PID: 2473652 Comm: Thread-8 Kdump: loaded Tainted: G W 4.19.90-23.8.v2101.ky10.x86_64 #1
Jun 30 23:33:27 txcdb174 kernel: [3648710.985354] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015
Jun 30 23:33:27 txcdb174 kernel: [3648710.985356] RIP: 0010:filp_close+0xbb/0xf0
Jun 30 23:33:27 txcdb174 kernel: [3648710.985357] Code: e4 48 89 df e8 96 67 00 00 5b 44 89 e0 5d 41 5c 41 5d c3 41 bd 01 00 00 00 45 31 e4 eb 98 48 c7 c7 40 f2 a7 b1 e8 b3 ca e5 ff <0f> 0b eb d0 48 8b 47 60 48 8b 73 20 48 8b 40 60 e8 50 5b 94 00 48
Jun 30 23:33:27 txcdb174 kernel: [3648710.985358] RSP: 0018:ffffb6b6a3a3ff10 EFLAGS: 00010282
Jun 30 23:33:27 txcdb174 kernel: [3648710.985359] RAX: 0000000000000024 RBX: ffff963a8afdf900 RCX: 0000000000000006
Jun 30 23:33:27 txcdb174 kernel: [3648710.985360] RDX: 0000000000000000 RSI: 0000000000000086 RDI: ffff96493e5d6890
Jun 30 23:33:27 txcdb174 kernel: [3648710.985361] RBP: ffff964a857a82c0 R08: 000000012f4c4337 R09: 0000000000000004
Jun 30 23:33:27 txcdb174 kernel: [3648710.985362] R10: ffffffffb1e610a0 R11: 0000000000000001 R12: 0000000000000000
Jun 30 23:33:27 txcdb174 kernel: [3648710.985363] R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000000
Jun 30 23:33:27 txcdb174 kernel: [3648710.985366] FS: 00007fd0dcdad700(0000) GS:ffff96493e5c0000(0000) knlGS:0000000000000000
Jun 30 23:33:27 txcdb174 kernel: [3648710.985367] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 30 23:33:27 txcdb174 kernel: [3648710.985368] CR2: 00007f0cd49d4000 CR3: 0000000f5f7de000 CR4: 00000000003406e0
Jun 30 23:33:27 txcdb174 kernel: [3648710.985370] Call Trace:
Jun 30 23:33:27 txcdb174 kernel: [3648710.985372] __x64_sys_close+0x1e/0x50
Jun 30 23:33:27 txcdb174 kernel: [3648710.985374] do_syscall_64+0x5b/0x1d0
Jun 30 23:33:27 txcdb174 kernel: [3648710.985376] entry_SYSCALL_64_after_hwframe+0x4Jun 30 23:36:20 txcdb174 kernel: [3648883.906944] RAX: ffffffffffffffda RBX: 00007fd0dcdabfd0 RCX: 00007fd21a0437bd
Jun 30 23:36:20 txcdb174 kernel: [3648883.906944] RDX: 00007fd21961d9b8 RSI: 00007fd2195f6fa0 RDI: 0000000000000008
Jun 30 23:36:20 txcdb174 kernel: [3648883.906945] RBP: 00007fd0dcdabfc0 R08: 00000000c903dfc0 R09: 00000000c903e018
Jun 30 23:36:20 txcdb174 kernel: [3648883.906946] R10: 00000000002ff638 R11: 0000000000000293 R12: 0000000000000042
Jun 30 23:36:20 txcdb174 kernel: [3648883.906947] R13: 0000000000000008 R14: 00007fd0b4009260 R15: 00007fd218cf5b30
Jun 30 23:36:20 txcdb174 kernel: [3648883.906951] —[ end trace d4aed3b8265a1aca ]—