Date: Thu, 30 Apr 2026 17:08:31 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 294903] zfs: assertion failure: VERIFY3U(offset, <, dn->dn_datablksz) failed (9223372036854775807 < 8704) Message-ID: <bug-294903-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294903 Bug ID: 294903 Summary: zfs: assertion failure: VERIFY3U(offset, <, dn->dn_datablksz) failed (9223372036854775807 < 8704) Product: Base System Version: 16.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: fuz@FreeBSD.org CC: bdrewery@FreeBSD.org, jhibbits@FreeBSD.org On a ppc64le FreeBSD 15.0 system with both UFS and ZFS, running a Poudriere bulk job under high system load, I get this crash: panic: VERIFY3U(offset, <, dn->dn_datablksz) failed (9223372036854775807 < 8704) cpuid = 2 time = 1777511631 KDB: stack backtrace: 0xc00800011a09f140: at vpanic+0x1ac 0xc00800011a09f1f0: at spl_panic+0x38 0xc00800011a09f220: at dbuf_whichblock+0xc0 0xc00800011a09f290: at dmu_evict_range+0xa4 0xc00800011a09f2f0: at zfs_space+0x68c4 0xc00800011a09f370: at VOP_ADVISE_APV+0x88 0xc00800011a09f3f0: at kern_posix_fadvise+0x21c 0xc00800011a09f4d0: at sys_posix_fadvise+0x38 0xc00800011a09f500: at trap+0xe64 0xc00800011a09f610: at trap+0x618 0xc00800011a09f740: at powerpc_interrupt+0x1cc 0xc00800011a09f7d0: user SC trap by 0x810d77110: srr1=0x900000000280f933 r1=0xfffffbfffd5c0 cr=0x22440a22 xer=0 ctr=0x810d77100 r2=0x810d913b0 frame=0xc00800011a09f800 KDB: enter: panic [ thread pid 45559 tid 324820 ] Stopped at kdb_enter+0x70: ori r0, r0, 0x0 db> Note that 9223372036854775807 is just 0x7fffffffffffffff, or LLONG_MAX. bdrewery thinks he has seen the same failure on an amd64 box, too. kernel crash dump available on request. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-294903-227>