Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 15 Sep 2024 22:46:32 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 281526] Linuxulator - fstatat unsupported flag 0x800
Message-ID:  <bug-281526-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281526

            Bug ID: 281526
           Summary: Linuxulator - fstatat unsupported flag 0x800
           Product: Base System
           Version: 14.1-STABLE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: misc
          Assignee: bugs@FreeBSD.org
          Reporter: sporran-musing0p@icloud.com

Created attachment 253594
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D253594&action=
=3Dedit
linux binary under linuxulator - NOK

Jails are great.
And Linux compatibility also working in jails is great.

I spent last 2 weeks learning how to use both.

I would love to move to FreeBSD + Jails, but have one binary (linux) that d=
oes
not want to work under linuxulator.
Currently, my main server runs Proxmox with LXC based virtual machines (ker=
nel
based, not full VM), and I was hoping to move to FreeBSD (just because I am
tired of Linux somehow, and want to move to something more consistent with
native zfs and no systemd).



I get this message when I try to run the linux compiled binary, in
/var/lob/messages
fstatat unsupported flag 0x800

and this is the symptom when I run the linux compiled binary

************************
EXCEPTION: Exception: type=3Dboost::filesystem::filesystem_error,
what=3D"boost::filesystem::status: Invalid argument [system:22]: "/root/.fi=
ro""
No debug information available for stacktrace. You should add debug informa=
tion
and then run:
firod
-printcrashinfo=3Dbvcgc43iinzgc43ijfxgm3ybaacwm2lsn5sierlymnsxa5djn5xduidup=
fygkplcn5xxg5b2hjtgs3dfon4xg5dfnu5duztjnrsxg6ltorsw2x3fojzg64rmeb3wqyluhurg=
e33pon2duotgnfwgk43zon2gk3j2hjzxiyluovztuicjnz3gc3djmqqgc4thovwwk3tuebnxg6l=
torsw2orsgjotuibcf5zg633uf4xgm2lsn4rcecbp7suqaaaaaaamsx3caaaaaaaaybwgeaaaaa=
aab64peaaaaaaaac63khaaaaaaaackwjzqccaaaaaalm3taeeaaaaarkcsaaaaaaaaaaa=3D

Assertion failure:
  assertion: pCurrentParams
  file: chainparams.cpp, line: 1283
  function: const CChainParams& Params()
No debug information available for stacktrace. You should add debug informa=
tion
and then run:
firod
-printcrashinfo=3Dbvcgc43iinzgc43ijfxgm3ybaacwm2lsn5shwqltonsxe5djn5xcaztbn=
fwhk4tfhifcaidbonzwk4tunfxw4oraobbxk4tsmvxhiudbojqw24ykeaqgm2lmmu5cay3imfuw=
44dbojqw24zomnyhalbanruw4zj2eayteobtbiqcaztvnzrxi2lpny5cay3pnzzxiicdinugc2l=
okbqxeylnomtcaudbojqw24zifef6ntdeaaaaaaaa6ovvwaaaaaaaaakupeaaaaaaac76woyaaa=
aaaafvay6aaaaaaaafbcjbaaaaaaaa5ojcaaaaaaaabpnvdqaaaaaaabfle4ybbaaaaaafwnzqc=
caaaaaivbjaaaaaaaaaaa=3D=3D=3D=3D=3D=3D
firod: chainparams.cpp:1283: const CChainParams& Params(): Assertion
`pCurrentParams' failed.
Aborted (core dumped)


I tried to re-compile it under FreeBSD directly, but it fails on some tor
library not present (different topic).

Other linux stuff I want to have running works fine in linux jails, and I s=
ee
even better memory/cpu usage than directly on linux.

So this is the one thing that holds me back from moving.

Any help would be appreciated
Attaching the strace from linux binary start, OK and NOK

--=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-281526-227>