Date: Wed, 27 Sep 2023 06:15:35 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 244899] zfs: xattr on a symlink target > 136 causes "bad file descriptor" (on 12.1) and panic on (13 CURRENT) in sa_build_index() Message-ID: <bug-244899-3630-JLVUNWPW1G@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-244899-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-244899-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=3D244899 Eugene M. Zheganin <eugene@zhegan.in> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eugene@zhegan.in --- Comment #14 from Eugene M. Zheganin <eugene@zhegan.in> --- Seems like most people stepping on this have nothing to do with storing por= ts on a symlinked tree. This is the only bug reported so far about this issue, thus it's synopsis is misleading. I've observed this on a 13.1 and 13.2, my ports tree is not symlinked, and = this happens to me on every large port like devel/llvm13 or www/firefox and is 1= 00% reproducible on "make extract", though the files and their number differ ea= ch time.=20 As stated earlier the only decent workaround so far is to build using tmpfs. This state can also be cleared for a while (several hours) by a reboot, but then it always comes back. There is an opinion that the latter could indicate that the issue lies in t= he vnode cache. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-244899-3630-JLVUNWPW1G>