log file full


Recommended Posts

Hey all, I've been migrating data from one server to another, and I've been using Krusader to move a share over to the new one, then Syncthing to ensure that the files moved are all the same/not corrupted etc.

Problem is, my LOG file is filling up, and when I download it i get a ton of this type of thing repeated over and over:

Apr 28 22:15:51 R170 kernel: WARNING: CPU: 5 PID: 16380 at lib/iov_iter.c:1203 iov_iter_pipe+0x11/0x33
Apr 28 22:15:51 R170 kernel: Modules linked in: md4 sha512_ssse3 sha512_generic cmac cifs libarc4 xt_mark xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle nf_tables vhost_net tun vhost vhost_iotlb tap xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 br_netfilter xfs md_mod ip6table_filter ip6_tables iptable_filter ip_tables x_tables bonding bnx2 intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel crypto_simd cryptd mpt3sas ipmi_ssif glue_helper i2c_core wmi input_leds intel_cstate raid_class led_class scsi_transport_sas acpi_power_meter intel_uncore i7core_edac ata_piix ipmi_si button [last unloaded: bnx2]
Apr 28 22:15:51 R170 kernel: CPU: 5 PID: 16380 Comm: file.so Tainted: G        W I       5.10.28-Unraid #1
Apr 28 22:15:51 R170 kernel: Hardware name: Dell Inc. PowerEdge R710/00NH4P, BIOS 6.4.0 07/23/2013
Apr 28 22:15:51 R170 kernel: RIP: 0010:iov_iter_pipe+0x11/0x33
Apr 28 22:15:51 R170 kernel: Code: 8b 4f 08 75 05 8b 56 08 eb 04 48 8b 56 08 48 29 ca 48 39 d0 48 0f 47 c2 c3 85 f6 74 02 0f 0b 8b 42 50 2b 42 54 39 42 5c 77 02 <0f> 0b c7 07 20 00 00 00 48 89 57 18 8b 42 50 48 c7 47 08 00 00 00
Apr 28 22:15:51 R170 kernel: RSP: 0018:ffffc90007943d38 EFLAGS: 00010246
Apr 28 22:15:51 R170 kernel: RAX: 0000000000000010 RBX: ffff888c57e7a100 RCX: 0000000000000000
Apr 28 22:15:51 R170 kernel: RDX: ffff888151788240 RSI: 0000000000000000 RDI: ffffc90007943d40
Apr 28 22:15:51 R170 kernel: RBP: ffff888c57e7a100 R08: 0000000000000000 R09: 0000000007943cc8
Apr 28 22:15:51 R170 kernel: R10: ffffc90007943cc8 R11: ffff889808514300 R12: 0000000000000104
Apr 28 22:15:51 R170 kernel: R13: ffffc90007943df0 R14: ffffc90007943e38 R15: 000000000007fefc
Apr 28 22:15:51 R170 kernel: FS:  00007f4691155800(0000) GS:ffff888c0fa80000(0000) knlGS:0000000000000000
Apr 28 22:15:51 R170 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 28 22:15:51 R170 kernel: CR2: 000055bb5d638230 CR3: 0000000171e94005 CR4: 00000000000206e0
Apr 28 22:15:51 R170 kernel: Call Trace:
Apr 28 22:15:51 R170 kernel: generic_file_splice_read+0x2c/0x15e
Apr 28 22:15:51 R170 kernel: splice_direct_to_actor+0xe4/0x1cd
Apr 28 22:15:51 R170 kernel: ? generic_file_splice_read+0x15e/0x15e
Apr 28 22:15:51 R170 kernel: do_splice_direct+0x94/0xbd
Apr 28 22:15:51 R170 kernel: do_sendfile+0x185/0x24f
Apr 28 22:15:51 R170 kernel: __do_sys_sendfile64+0x61/0xa7
Apr 28 22:15:51 R170 kernel: do_syscall_64+0x5d/0x6a
Apr 28 22:15:51 R170 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Apr 28 22:15:51 R170 kernel: RIP: 0033:0x7f469460a68e
Apr 28 22:15:51 R170 kernel: Code: c3 0f 1f 00 4c 89 d2 4c 89 c6 e9 bd fd ff ff 0f 1f 44 00 00 31 c0 c3 0f 1f 44 00 00 f3 0f 1e fa 49 89 ca b8 28 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d d2 a7 0c 00 f7 d8 64 89 01 48
Apr 28 22:15:51 R170 kernel: RSP: 002b:00007ffe050916d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
Apr 28 22:15:51 R170 kernel: RAX: ffffffffffffffda RBX: 00007ffe05091790 RCX: 00007f469460a68e
Apr 28 22:15:51 R170 kernel: RDX: 00007ffe050917b0 RSI: 0000000000000005 RDI: 0000000000000007
Apr 28 22:15:51 R170 kernel: RBP: 00007ffe05111b20 R08: 0000000000000000 R09: 0000000000000001
Apr 28 22:15:51 R170 kernel: R10: 0000000000080000 R11: 0000000000000246 R12: 00007ffe05091780
Apr 28 22:15:51 R170 kernel: R13: 00007ffe050917b0 R14: 00007ffe05091748 R15: 00007ffe05091740

 

I have attached my full log file below, and any help would be appreciated!

r170-diagnostics-20210430-0905.zip

Link to comment
59 minutes ago, Squid said:

Stop Krusader and see if the traces stop.

 

After that, I'd run a MemTest and post in the applicable support thread for Krusader

OK will do. I'm about 98% through a big move, so going to wait for that to finish, then run the memtest which can take a while, so will report back when that's done.

I also realized my BIOS was version 6.4.0 and not 6.6, so going to do that update as well.

Edited by cyriouslydylan
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.