Date: Wed, 20 May 2026 21:01:26 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 275731] panic in zfs: VERIFY(buf[i] == 0) failed Message-ID: <bug-275731-227-ALXuyP2A2p@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275731-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275731 John F. Carr <jfc@mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=2953 | |77 --- Comment #4 from John F. Carr <jfc@mit.edu> --- I am convinced now that this is a bug with deduplication. If I leave dedup=verify and disable the buf[0] assertion I get file corruption during a parallel build, a .o file is full of nulls. The exact file is unpredictable. If I set dedup=off on the active filesystems everything is fine. No assertion and no data loss. Tested on 15 and CURRENT. Sometimes the data that should be 0 appears to be ASCII text interpreted as a 64 bit integer. -- 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-275731-227-ALXuyP2A2p>