Date: Mon, 19 Jun 2023 15:38:00 +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-tN9u3fCRKt@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 --- Comment #10 from Jimmy Olgeni <olgeni@FreeBSD.org> --- Just a quick note that I'm seeing this regularly on some VMs, and physical hosts to a lesser degree. For some reason running "pkg upgrade" on py39-ansible seems to be a sure wa= y to trigger this on the affected boxes. =3D=3D=3D The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: py39-ansible: 7.1.0 -> 7.6.0 Number of packages to be upgraded: 1 The process will require 10 MiB more space. [1/1] Upgrading py39-ansible from 7.1.0 to 7.6.0... [1/1] Extracting py39-ansible-7.6.0: 38% pkg: Fail to chmod /usr/local/lib/python3.9/site-packages/ansible_collections/community/genera= l/plugins/modules/__pycache__/.pkgtemp.django_manage.cpython-39.pyc.ub2f8mx= mwp9S:Bad file descriptor [1/1] Extracting py39-ansible-7.6.0: 100% =3D=3D=3D The affected path is never the same. I ran "script LOG truss -f pkg upgrade -y py39-ansible" in the hope of gett= ing useful data - it was very slow but it worked on the first try, so there may= be some timing issue involved? :| --=20 You are receiving this mail because: You are on the CC list for the bug. 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-244899-3630-tN9u3fCRKt>