Date: Sat, 23 Apr 2022 22:03:01 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 263501] zdb failure: zdb failed to hold dataset 'tank/ROOT/default': No such file or directory Message-ID: <bug-263501-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263501 Bug ID: 263501 Summary: zdb failure: zdb failed to hold dataset 'tank/ROOT/default': No such file or directory Product: Base System Version: 13.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: mason@blisses.org In BZ#263407 it seems that the bootloader struggles to deal with files with holes immediately after them. In that bug's comments, kevans noted zdb=20 output that displays the properties of affected and unaffected files, doing something like this: # zdb -vvvvvvO tank/ROOT/default boot/kernel/geom_eli.ko Unfortunately, while this works for OpenZFS built for Debian, on FreeBSD 13.0, and on FreeBSD 12, I'm finding that it consistently fails on 13.1=20 installs, giving me this message: zdb failed to hold dataset 'tank/ROOT/default': No such file or directo= ry My immediate concern is that 13.1-RC4 doesn't display the bad behaviour=20 from the original bug, so testing a fix will involve contructing a file to match the problematic pattern, using posix-fallocate or or ftruncate or=20 somesuch. However, without being able to use zdb, it'll be significantly more difficult to verify that the file(s) in question match the pattern or not. --=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-263501-227>