Date: Sat, 11 Jun 2022 15:25:55 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 264617] Panic: Invalid dnode block MAC Message-ID: <bug-264617-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D264617 Bug ID: 264617 Summary: Panic: Invalid dnode block MAC Product: Base System Version: 13.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: gldisater@gmail.com Using syncoid to replicate an unencrypted zfs dataset to a ZFS encrypted dataset. root@apollo:/var/crash # kgdb /boot/kernel/kernel /var/crash/vmcore.0 GNU gdb (GDB) 12.1 [GDB v12.1 for FreeBSD] Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.htm= l> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-portbld-freebsd13.0". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /boot/kernel/kernel... Reading symbols from /usr/lib/debug//boot/kernel/kernel.debug... Unread portion of the kernel message buffer: panic: Invalid dnode block MAC cpuid =3D 10 time =3D 1654958850 KDB: stack backtrace: #0 0xffffffff80c69465 at kdb_backtrace+0x65 #1 0xffffffff80c1bb1f at vpanic+0x17f #2 0xffffffff80c1b993 at panic+0x43 #3 0xffffffff821d8063 at dbuf_sync_leaf+0x643 #4 0xffffffff821d76eb at dbuf_sync_list+0xcb #5 0xffffffff821d7951 at dbuf_sync_indirect+0x141 #6 0xffffffff821d76ac at dbuf_sync_list+0x8c #7 0xffffffff821d7951 at dbuf_sync_indirect+0x141 #8 0xffffffff821d76ac at dbuf_sync_list+0x8c #9 0xffffffff821d7951 at dbuf_sync_indirect+0x141 #10 0xffffffff821d76ac at dbuf_sync_list+0x8c #11 0xffffffff821d7951 at dbuf_sync_indirect+0x141 #12 0xffffffff821d76ac at dbuf_sync_list+0x8c #13 0xffffffff821d7951 at dbuf_sync_indirect+0x141 #14 0xffffffff821d76ac at dbuf_sync_list+0x8c #15 0xffffffff8220116b at dnode_sync+0xacb #16 0xffffffff821e7117 at dmu_objset_sync+0x197 #17 0xffffffff82206f29 at dsl_dataset_sync+0x169 Uptime: 25d19h50m52s Dumping 10298 out of 65093 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%.= .91% __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:55 55 __asm("movq %%gs:%P1,%0" : "=3Dr" (td) : "n" (offsetof(stru= ct pcpu, (kgdb) quit root@apollo:/var/crash # uname -a FreeBSD apollo 13.1-RELEASE FreeBSD 13.1-RELEASE releng/13.1-n250148-fc952ac2212 GENERIC amd64 root@apollo:/var/crash # Destination dataset was corrupted after the crash: root@apollo:/var/crash # zpool status -v pool: spinners state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A scan: scrub repaired 0B in 01:38:53 with 0 errors on Tue May 3 11:53:21 = 2022 config: NAME STATE READ WRITE CKSUM spinners ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 da1 ONLINE 0 0 0 da3 ONLINE 0 0 0 errors: Permanent errors have been detected in the following files: =20=20=20=20=20=20=20 spinners/encrypted/vm/tplink-omada/disk0@autosnap_2022-06-01_23:59:04_daily= :<0x0> --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-264617-227>