[Bug 244899] [PATCH] zfs: xattr on a symlink target > 136 causes "bad file descriptor" (on 12.1) and panic on (13 CURRENT) in sa_build_index()
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 21 Sep 2022 08:50:19 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244899 Sean Champ <lab+bsd@thinkum.space> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lab+bsd@thinkum.space --- Comment #7 from Sean Champ <lab+bsd@thinkum.space> --- I think this may have cleared up at least in FreeBSD 13.1 (changeset b63021e001d)? e.g uname FreeBSD sol.cloud.thinkum.space 13.1-STABLE FreeBSD 13.1-STABLE #0 build/stable/13-n252436-b63021e001d: Sun Sep 18 22:01:30 PDT 2022 me@sol.cloud.thinkum.space:[sic] amd64 With an earlier build of FreeBSD 13.1 (changeset 41ce229505a) I'd encountered what I think was the same error as here, when building some ports with poudriere on ZFS. With that earlier FreeBSD 13.1 build, the uname: FreeBSD sol.cloud.thinkum.space 13.1-STABLE FreeBSD 13.1-STABLE #0 build/stable/13-n251001-41ce229505a: Sat Jun 4 18:12:09 PDT 2022 me@sol.cloud.thinkum.space:[sic] amd64 The "Bad file descriptor" error, when building lang/rust under Poudriere on ZFS on that kernel and base system: [...] -- Installing: /wrkdirs/usr/ports/lang/rust/work/_build/x86_64-unknown-freebsd/llvm/include/llvm/MC/MCObjectFileInfo.h CMake Error at cmake_install.cmake:41 (file): file INSTALL cannot copy file "/wrkdirs/usr/ports/lang/rust/work/rustc-1.63.0-src/src/llvm-project/llvm/include/llvm/MC/MCObjectFileInfo.h" to "/wrkdirs/usr/ports/lang/rust/work/_build/x86_64-unknown-freebsd/llvm/include/llvm/MC/MCObjectFileInfo.h": Bad file descriptor. FAILED: CMakeFiles/install.util cd /wrkdirs/usr/ports/lang/rust/work/_build/x86_64-unknown-freebsd/llvm/build && /usr/local/bin/cmake -P cmake_install.cmake ninja: build stopped: subcommand failed. I'd seen a similar error with a number of ports - "Bad file descriptor" - before stopping the port upgrade. Now having updated the local 13.1 build to changeset b63021e001d under stable/13 branch, I've not seen any such error when building rust now. Of course, it will be a few more hours before the entire port upgrade completes, if it could serve any test of the issue. If it may show up again, but I'll look at adding those options to my KERNCONF and rebuilding the kernel. Thx! -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.