Kernel warning detected during copy on NFS disk 6.4.15-2-Liquorix
antdeveloper
Status: Interested
Joined: 10 Mar 2023
Posts: 15
Reply Quote
Hi,
I noticed that by copying a large file via client on a mounted nfs disk, on the nfs server, during the copy, a warning returns (see below).
The client freezes and returns this error in the journal: "NFSV4: State Recovery Failed for Open file ISO/.uruk -Cinnamon_3.0.iso, Error = -116"
The kernel installed on the nfs server is: "6.4.15-2-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 6.4-20.1~bookworm (2023-09-07) x86_64", on a Debian/Bookworm installation.
I used RSYNC to align: local disk directory -> remote directory on nfs server, locally mounted in nfs.
Thank you,
Antonio

---

:: Code ::
set 12 08:20:36 NASSERVER kernel: ------------[ cut here ]------------
set 12 08:20:36 NASSERVER kernel: NETDEV WATCHDOG: ens5 (r8169): transmit queue 0 timed out 5878 ms
set 12 08:20:36 NASSERVER kernel: WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:525 dev_watchdog+0x2ae/0x2c0
set 12 08:20:36 NASSERVER kernel: Modules linked in: rpcsec_gss_krb5 nouveau mxm_wmi i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec ppdev rc_core snd_intel8x0 snd_ac97_codec drm_kms_helper ac97_bus syscopyarea sysfillrect snd_pcm sysimgblt snd_timer agpgart video snd intel_powerclamp parport_pc soundcore parport pcspkr serio_raw joydev wmi_bmof e752x_edac sg smsc47b397 dm_crypt encrypted_keys trusted asn1_encoder nfsd tee auth_rpcgss tpm rng_core nfs_acl lockd grace drm fuse loop sunrpc efi_pstore zram dmi_sysfs ip_tables x_tables ext4 crc16 mbcache jbd2 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid0 multipath linear dm_mod raid1 md_mod sr_mod cdrom ata_generic pata_acpi firewire_ohci mptspi psmouse mptscsih usbhid ata_piix firewire_core crc_itu_t e1000 mptbase r8169 scsi_transport_spi realtek wmi
set 12 08:20:36 NASSERVER kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.4.15-2-liquorix-amd64 #1  liquorix 6.4-20.1~bookworm
set 12 08:20:36 NASSERVER kernel: Hardware name: Hewlett-Packard hp workstation xw8200/08B4h, BIOS 786B8 v2.02 06/02/2005
set 12 08:20:36 NASSERVER kernel: RIP: 0010:dev_watchdog+0x2ae/0x2c0
set 12 08:20:36 NASSERVER kernel: Code: fe ff ff 48 89 ef c6 05 18 aa d6 00 01 e8 fa f7 f9 ff 45 89 f8 44 89 f1 48 89 ee 48 89 c2 48 c7 c7 00 9a 6c 82 e8 22 45 49 ff <0f> 0b e9 af fe ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90
set 12 08:20:36 NASSERVER kernel: RSP: 0018:ffffc90000104ea8 EFLAGS: 00010282
set 12 08:20:36 NASSERVER kernel: RAX: 0000000000000000 RBX: ffff88800543841c RCX: 0000000000000000
set 12 08:20:36 NASSERVER kernel: RDX: ffff88807aaac440 RSI: ffff88807aaa0240 RDI: 0000000000000300
set 12 08:20:36 NASSERVER kernel: RBP: ffff888005438000 R08: 0000000000000001 R09: 00000000ffffffea
set 12 08:20:36 NASSERVER kernel: R10: ffffffff8284ee00 R11: 0000000000000355 R12: ffff8880054384c8
set 12 08:20:36 NASSERVER kernel: R13: ffff88807ab3f800 R14: 0000000000000000 R15: 00000000000016f6
set 12 08:20:36 NASSERVER kernel: FS:  0000000000000000(0000) GS:ffff88807aa80000(0000) knlGS:0000000000000000
set 12 08:20:36 NASSERVER kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
set 12 08:20:36 NASSERVER kernel: CR2: 00007f514f3840d8 CR3: 0000000005616000 CR4: 00000000000006e0
set 12 08:20:36 NASSERVER kernel: Call Trace:
set 12 08:20:36 NASSERVER kernel:  <IRQ>
set 12 08:20:36 NASSERVER kernel:  ? __warn+0x7d/0x1a0
set 12 08:20:36 NASSERVER kernel:  ? dev_watchdog+0x2ae/0x2c0
set 12 08:20:36 NASSERVER kernel:  ? report_bug+0x1fe/0x270
set 12 08:20:36 NASSERVER kernel:  ? handle_bug+0x41/0x70
set 12 08:20:36 NASSERVER kernel:  ? exc_invalid_op+0x15/0xc0
set 12 08:20:36 NASSERVER kernel:  ? asm_exc_invalid_op+0x16/0x20
set 12 08:20:36 NASSERVER kernel:  ? dev_watchdog+0x2ae/0x2c0
set 12 08:20:36 NASSERVER kernel:  ? dev_watchdog+0x2ae/0x2c0
set 12 08:20:36 NASSERVER kernel:  ? __queue_work+0x164/0x490
set 12 08:20:36 NASSERVER kernel:  ? __pfx_dev_watchdog+0x10/0x10
set 12 08:20:36 NASSERVER kernel:  call_timer_fn+0x27/0x130
set 12 08:20:36 NASSERVER kernel:  run_timer_softirq+0x3d6/0xaa0
set 12 08:20:36 NASSERVER kernel:  ? __pfx_dev_watchdog+0x10/0x10
set 12 08:20:36 NASSERVER kernel:  ? __pfx_read_tsc+0x10/0x10
set 12 08:20:36 NASSERVER kernel:  ? ktime_get+0x38/0xa0
set 12 08:20:36 NASSERVER kernel:  ? __pfx_native_apic_mem_write+0x10/0x10
set 12 08:20:36 NASSERVER kernel:  ? lapic_next_event+0x1c/0x30
set 12 08:20:36 NASSERVER kernel:  ? clockevents_program_event+0x95/0x100
set 12 08:20:36 NASSERVER kernel:  __do_softirq+0xc6/0x2a1
set 12 08:20:36 NASSERVER kernel:  irq_exit_rcu+0x83/0xb0
set 12 08:20:36 NASSERVER kernel:  sysvec_apic_timer_interrupt+0x6e/0x90
set 12 08:20:36 NASSERVER kernel:  </IRQ>
set 12 08:20:36 NASSERVER kernel:  <TASK>
set 12 08:20:36 NASSERVER kernel:  asm_sysvec_apic_timer_interrupt+0x16/0x20
set 12 08:20:36 NASSERVER kernel: RIP: 0010:pv_native_safe_halt+0xb/0x10
set 12 08:20:36 NASSERVER kernel: Code: 0b 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 eb 07 0f 00 2d 19 6b 3c 00 fb f4 <c3> cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 8b
set 12 08:20:36 NASSERVER kernel: RSP: 0018:ffffc900000b7e60 EFLAGS: 00000246
set 12 08:20:36 NASSERVER kernel: RAX: 0000000000004000 RBX: ffff88800414b064 RCX: 4000000000000000
set 12 08:20:36 NASSERVER kernel: RDX: ffff88807aa80000 RSI: ffff88800414b000 RDI: 0000000000000001
set 12 08:20:36 NASSERVER kernel: RBP: ffff88800414b064 R08: ffffffff82919540 R09: 0000000027ffa440
set 12 08:20:36 NASSERVER kernel: R10: 0000000000000008 R11: 0000000000002d7e R12: ffffffff82919540
set 12 08:20:36 NASSERVER kernel: R13: 0000000000000001 R14: ffffffff829195c0 R15: 0000000000000000
set 12 08:20:36 NASSERVER kernel:  acpi_safe_halt+0x15/0x30
set 12 08:20:36 NASSERVER kernel:  acpi_idle_do_entry+0x2f/0x50
set 12 08:20:36 NASSERVER kernel:  acpi_idle_enter+0x7b/0xd0
set 12 08:20:36 NASSERVER kernel:  cpuidle_enter_state+0x80/0x820
set 12 08:20:36 NASSERVER kernel:  cpuidle_enter+0x29/0x40
set 12 08:20:36 NASSERVER kernel:  do_idle+0x1ce/0x230
set 12 08:20:36 NASSERVER kernel:  cpu_startup_entry+0x19/0x20
set 12 08:20:36 NASSERVER kernel:  start_secondary+0x103/0x110
set 12 08:20:36 NASSERVER kernel:  secondary_startup_64_no_verify+0xf9/0xfb
set 12 08:20:36 NASSERVER kernel:  </TASK>
set 12 08:20:36 NASSERVER kernel: ---[ end trace 0000000000000000 ]---

Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4124
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
I don't know if this is related, but NFS has had a long standing issue of not supporting modern Linux file data completely, leading to failures in unpredictable ways when using rsync.

i actually stopped doing network NFS / rsync backups because of this issue. There's some file system features in newer file systems that nfs does not know about.

Not sure if this is your issue or not, but it's worth mentioning.

I believe rsync over ssh does not have this issue, because it's an NFS issue, not an rsync issue.

Try doing the same rsync action over ssh and see if you get the same results, that might be useful information.
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 1116
Reply Quote
I released a v6.5 kernel (6.5.3 specifically), yesterday, can you give it a try?
Back to top
Display posts from previous:   

All times are GMT - 8 Hours