Date: Mon, 06 Jan 2025 22:47:19 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 283888] makefs Assertion Failed: makefs/zfs/fs.c, line 190 Message-ID: <bug-283888-3630-KTwLvPIyae@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-283888-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-283888-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283888 Mark Johnston <markj@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open --- Comment #2 from Mark Johnston <markj@FreeBSD.org> --- I tried opening the core dump using 14.2 debug symbols, but it's unusable.= =20 Where did you makefs binary come from? The assertion is saying that makefs, while traversing the input directory hierarchy, encountered something that isn't a regular file, a directory, or= a symlink. So, probably a unix socket or a fifo. I can see in walk.c (not specific to ZFS) that sockets are skipped, so there's probably a fifo in th= ere somewhere. Can you confirm whether that's the case? makefs -t ffs works fine with fifos, so I suppose we should handle them in = the ZFS backend too, but it'd be nice to confirm that that's the actual problem here. (In reply to Michael Dexter from comment #1) That would be unrelated. Did you do anything to the pool before you export= ed it? --=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-283888-3630-KTwLvPIyae>