[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()

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244899

--- Comment #9 from Sean Champ <lab+bsd@thinkum.space> ---
After rebuilding the kernel from changeset b63021e001d in stable/13 with the
additional makeoptions, still seeing the similar (?) error in port builds with
ZFS in Poudriere

~~~~
===>   Returning to build of binutils-2.37_4,1
===>   binutils-2.37_4,1 depends on executable: msgfmt - not found
===>   Installing existing package /packages/All/gettext-tools-0.21_1.pkg
[xmin.bld.cloud.thinkum.space] Installing gettext-tools-0.21_1...
[xmin.bld.cloud.thinkum.space] `-- Installing libtextstyle-0.21...
[xmin.bld.cloud.thinkum.space] `-- Extracting libtextstyle-0.21: ..........
done
[xmin.bld.cloud.thinkum.space] Extracting gettext-tools-0.21_1: ....
pkg-static: Fail to chown
/usr/local/share/doc/gettext/examples/hello-java-awt/po/.pkgtemp.zh_HK.po.BfvtcrBEkY7V:Bad
file descriptor
[xmin.bld.cloud.thinkum.space] Extracting gettext-tools-0.21_1... done

Failed to install the following 1 package(s):
/packages/All/gettext-tools-0.21_1.pkg
*** Error code 1

Stop.
make: stopped in /usr/ports/devel/binutils
~~~~

Albeit, the symlink example above is not erring here. 

I've noticed the bug - as above - at some points, with symlink files.
Previously, it was happening during pkg staging.

Once installed under a builder jail, the file
/usr/local/share/doc/gettext/examples/hello-java-awt/po/zh_HK.po is not a
symlink.

After some previous occurrences of the bug, during pkg staging in poudriere,
I'd thought that it might be related to the item above. Maybe it's a separate
bug of some kind.

The 'Bad file descriptor' message continues to show up in port builds locally,
when using ZFS in poudriere. There's a workaround in using tmpfs for all
builder filesystems in poudriere builds. 

I'll try to make an isolated test case for the bug that I'm seeing with my
local FreeBSD build - something beyond the bad FD messages here.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.