On 2025-04-12 21:22 -04:00 EDT, "Tomoaki AOKI"
wrote:
> On Sat, 12 Apr 2025 23:35:02 +0000 (UTC)
> "Alexander Ziaee" wrote:
>
>> Hello,
>>
>> I'd like to enable spleen 64 in the build. It provides 80x25 character
>> console on my 14
Hello,
I'd like to enable spleen 64 in the build. It provides 80x25 character console
on my 14" 2560x1600 display. I don't understand Makefile very well, but it is
working on my machine. Attached is the review.
[0]: https://reviews.freebsd.org/D49768
Best,
Alex
till might be a software
issue, but I can't say much about that area.
--
Alexander Motin
ke to dig into
Illumos code, but I exactly thought about it as a source of ideas about
original Solaris attributes. I am regularly going there myself when I
need to understand some pre-ZoL concepts. I've never had Illumos or
Solaris installed though.
--
Alexander Motin
eing implemented for Solaris decades ago, and
considering limitations other systems including FreeBSD have. It just
might be a bit tangled after the years.
--
Alexander Motin
ile importing the pool as read-only, which should
not access or at least update the quotas.
--
Alexander Motin
he panic occurs shortly after.
My kdb backtrace log is attached to this url.
<https://ibb.co/v6d4Kr7K <https://ibb.co/v6d4Kr7K>>
I'm using FreeBSD 15.0-CURRENT main-n275975-5963423232e8.
The link does not open, proposing to upgrade for Pro account.
--
Alexander Motin
Am 2025-03-15 14:33, schrieb Kyle Evans:
[+grembo@ for iocage]
On 3/15/25 06:26, Alexander Leidinger wrote:
Am 2025-02-26 16:20, schrieb Alexander Leidinger:
Hi,
the working system is from 2025-01-25-141603, the non working system
is from 2025-02-21-115311.
I'm not sure what the iss
Am 2025-02-26 16:20, schrieb Alexander Leidinger:
Hi,
the working system is from 2025-01-25-141603, the non working system is
from 2025-02-21-115311.
I'm not sure what the issue is exactly. I have traced down the change
of behavior to
---snip---
if not LIBC.setfstab(fstab_file_path.e
initial commit.
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
signature.asc
Description: OpenPGP digital signature
Am 2025-02-21 22:31, schrieb Mark Johnston:
On Thu, Feb 20, 2025 at 10:27:28AM +0100, Alexander Leidinger wrote:
Hi,
I get this backtrace:
---snip---
[102] panic: invalid local group size 16 and count 16
[102] cpuid = 17
[102] time = 1740041984
[102] KDB: stack backtrace:
[102
Am 2025-02-20 10:27, schrieb Alexander Leidinger:
Hi,
I get this backtrace:
---snip---
[102] panic: invalid local group size 16 and count 16
[102] cpuid = 17
[102] time = 1740041984
[102] KDB: stack backtrace:
[102] db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame
0xfe07453a5b80
at 2025-02-20-080119 CET. The previous world
is from 1 month ago (2025-01-22-120655).
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
signature.asc
Description: OpenPGP digital
nt to improve FreeBSD, sometimes it works on
first try, sometimes we need to try more often.
Bye,
Alexander.
-Max
On Tue, Jan 28, 2025, 7:05 PM Alexander Leidinger
wrote:
Am 2025-01-28 18:32, schrieb Maxim Sobolev:
I also think this should be reverted back to default. "-n" refers
This was discussed in the review referenced in the commit. The -nn
proposal was there too. Personally I agree with the rationales in favor
of "-nn".
Bye,
Alexander.
-Max
On Tue, Jan 28, 2025, 5:46 PM Gleb Smirnoff
wrote:
On Sun, Jan 26, 2025 at 04:58:57PM +0100, Alexander Lei
Am 2025-01-26 16:58, schrieb Alexander Leidinger:
Hi,
something has changed in the output of "netstat -rn" between
2024-11-23-195545 and 2025-01-22-151306. The default route is not
listed as "default" anymore, but with "0.0.0.0" resp. "::/0". This
brea
I'm not sure if it uses netstat
or some other interface, so it may not be directly related to netstat
itself but could be related to some other stuff (netlink maybe?).
Does this ring a bell for someone?
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F3
://reviews.freebsd.org/D48426
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
signature.asc
Description: OpenPGP digital signature
a, rsp =
0x2f2048e41cf8, rbp = 0x2f2048e41d60 ---
KDB: enter: panic
[ thread pid 999 tid 100184 ]
Stopped at kdb_enter+0x33: movq $0,0x10538d2(%rip)
db>
--
Alexander Motin
Am 2024-11-22 19:09, schrieb Ed Maste:
On Fri, 22 Nov 2024 at 12:48, Ed Maste wrote:
On Fri, 22 Nov 2024 at 09:32, Alexander Leidinger
wrote:
>
> FORTIFY_SOURCE=2 ## <--- maybe this? if yes: regression!
Yes this is very likely -- looking
Sorry about that -- now
Am 2024-11-22 18:19, schrieb Shawn Webb:
On Fri, Nov 22, 2024 at 04:20:42PM +0100, Alexander Leidinger wrote:
Am 2024-11-22 15:31, schrieb Alexander Leidinger:
> Am 2024-11-22 14:08, schrieb Ed Maste:
> > On Thu, 21 Nov 2024 at 04:43, Alexander Leidinger
> > wrote:
Am 2024-11-22 15:31, schrieb Alexander Leidinger:
Am 2024-11-22 14:08, schrieb Ed Maste:
On Thu, 21 Nov 2024 at 04:43, Alexander Leidinger
wrote:
Hi,
I get:
ld: error: version script assignment of 'FBSD_1.5' to symbol
'getentropy' failed: symbol not defined
cc: error: l
on arm64- Orange Pi 5 Plus.
Does it boot when you revert this change?
https://cgit.freebsd.org/src/commit/?id=c87b3f0006be9ac5813f1ff636f18c9b4a41b08e
If yes, please comment on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282493
Bye,
Alexander.
--
http://www.Leidinger.net alexan
Am 2024-11-22 14:08, schrieb Ed Maste:
On Thu, 21 Nov 2024 at 04:43, Alexander Leidinger
wrote:
Hi,
I get:
ld: error: version script assignment of 'FBSD_1.5' to symbol
'getentropy' failed: symbol not defined
cc: error: linker command failed with exit code 1 (use -v to s
m 2024-11-13 18:34pm UTC.
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
signature.asc
Description: OpenPGP digital signature
Am 2024-11-17 19:28, schrieb Dimitry Andric:
On 17 Nov 2024, at 16:30, Alexander Leidinger
wrote:
Hi,
after reading
https://security.googleblog.com/2024/11/retrofitting-spatial-safety-to-hundreds.html
https://libcxx.llvm.org/Hardening.html
https://best.openssf.org/Compiler
or disabled by default?
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
signature.asc
Description: OpenPGP digital signature
Am 2024-11-08 14:27, schrieb Warner Losh:
On Fri, Nov 8, 2024, 12:34 AM Alexander Leidinger
wrote:
Am 2024-11-08 05:46, schrieb Warner Losh:
OK. I'm confused... but no matter.
Three more things to help...
(1) kenv after boot with a fixed kernel
COLUMNS="100"
LINES="
os.system.uuid="14fd7a5a-8f68-44d4-88b6-68498f8b55fb"
smbios.system.version="virt-4.2"
smbios.version="3.0"
splash="/boot/images/freebsd-logo-rev.png"
splash_bmp_load="NO"
splash_pcx_load="NO"
splash_txt_load="NO"
tcp_rack_load=&q
Am 2024-11-07 20:59, schrieb Warner Losh:
On Wed, Nov 6, 2024 at 3:41 AM Alexander Leidinger
wrote:
Am 2024-11-02 17:08, schrieb Warner Losh:
On Sat, Nov 2, 2024, 10:03 AM Alexander Leidinger
wrote: Am 2024-10-30 22:11, schrieb Alexander
Leidinger:
WARNING! Trying to fire up the
Am 2024-11-02 17:08, schrieb Warner Losh:
On Sat, Nov 2, 2024, 10:03 AM Alexander Leidinger
wrote:
Am 2024-10-30 22:11, schrieb Alexander Leidinger:
WARNING! Trying to fire up the kernel, but no device tree blob found!
For anyone interested, I opened
https://bugs.freebsd.org/bugzilla
Am 2024-11-02 17:08, schrieb Warner Losh:
On Sat, Nov 2, 2024, 10:03 AM Alexander Leidinger
wrote:
Am 2024-10-30 22:11, schrieb Alexander Leidinger:
WARNING! Trying to fire up the kernel, but no device tree blob found!
For anyone interested, I opened
https://bugs.freebsd.org/bugzilla
Am 2024-10-30 22:11, schrieb Alexander Leidinger:
WARNING! Trying to fire up the kernel, but no device tree blob found!
For anyone interested, I opened
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282493 for this.
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net
a device tree is the normal case for ACPI based booting.
I do find this part of the messaging for an ACPI-based boot
misleading.
It doesn't boot at all. It hangs after this message.
The previous BE boots just fine, so something is broken.
Bye,
Alexander.
--
http://www.Leidinger.net al
NETLINK
options TCP_RFC7413
---snip---
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
signature.asc
Description: OpenPGP digital signature
world, only for ports. For the world/kernel build it's really the -j option.
Bye,
Alexander.
--
Send from a mobile device, please forgive brevity and misspellings.
Am 28. Oktober 2024 02:50:38 schrieb "Maku Bex" :
Hi David,
* What (if any) "max_jobs" (make's &qu
), rip = 0x3fa386c2a8fa, rsp =
0x3fa379d24b38, rbp = 0x3fa379d24ba0 ---
Uptime: 28s
--
Alexander Motin
On 2024-08-24 16:10 -04:00 EDT, "Ronald Klop" wrote:
> Van: Alexander Ziaee
>> On a new laptop GENERIC sometimes hangs on `enabling pf`.
> What version of freebsd?
1500023 amd64/sys/generic
> Do you have a pf config?
set skip on lo0
block in
pass out
> If it h
Hi everyone,
On a new laptop GENERIC sometimes hangs on `enabling pf`. When it does,
ctrl-alt-del or the power button will begin power off, but hangs on
`uhub0:detached` after `uptime: 6m39s`. Sometimes it does this multiple boots
in a row. Usually at least once out of every ten times.
My old
On 2024-08-13 17:51 -04:00 EDT, "Shawn Webb" wrote:
> On Tue, Aug 13, 2024 at 09:45:54PM UTC, Alexander Ziaee wrote:
>> Compiling freebsd-current/generic at head commit 6481b4 on
>> freebsd-current/generic from July 11th after a `make cleanworld` panics on
>> bar
Hello,
Compiling freebsd-current/generic at head commit 6481b4 on
freebsd-current/generic from July 11th after a `make cleanworld` panics on bare
metal boot on a thinkpad x230. It doesn't have a swap, so I don't have a dump.
Here is the trace:
db> bt
Tracing pid 21935 tid 100228 td 0xf9000
Am 2024-07-15 03:05, schrieb Alexander Ziaee:
Eventually, you want to learn to snapshot your system when you're
touching critical directories. Then, it never matters. You can just
roll back stressfree.
Specific to updates and if on ZFS: man bectl
Even better than snapshots.
Bye,
Alex
Hello!
> I made a big mess here.
> I (deleted my system libraries)
If I have no snapshots:
- boot into the installer
- mount
- copy /usr/*
It's not good, but it's good enough to get going to restore from backup or
makeworld at your leisure.
Eventually, you want to learn to snapshot your system
le the IPs, as long as the mangling is a consistent
replacement and not a cut-off).
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
signature.asc
Description: OpenPGP digital signature
h use ZFS may want to have
https://cgit.FreeBSD.org/src/commit/?id=4c053c17f2c8a715988f215d16284879857ca376
Apart from that much more stable on my 30-jails + poudriere host than
the src as from the middle of the month.
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger
Am 2024-05-22 22:45, schrieb Alexander Leidinger:
Am 2024-05-22 20:53, schrieb Warner Losh:
First order:
Looks like we're trying to schedule a trim, but that fails due to a
malloc issue. So then, since it's a
malloc issue, we wind up trying to automatically reschedule this I
-17-084543.
Full logs available at https://wiki.leidinger.net/core.txt.7 (1.1 MB).
This was in the middle of the night, poudriere was running.
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.
p I didn't run poudriere
anymore.
If so, can you test this patch?
I give it a try tomorrow anyway, and I will try to stress the system
again with poudriere.
The nvme is a cache and also a log device for a zpool, so not really a
deterministic way to trigger access to it.
Bye,
Alex
---
This is with a world from 2024-05-17-084543.
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
signature.asc
Description: OpenPGP digital signature
gests.
Without that context, it seems like what the proposed sysctl reports
is indirectly just the average size of free list entries. We could
just report that.
The calculation of the value is part of a bigger picture. The value
returned is used by some other code to make decisions.
Bye,
A
Am 2024-05-08 18:45, schrieb Bojan Novković:
Hi,
On 5/7/24 14:02, Alexander Leidinger wrote:
Hi,
I created some graphs of the memory fragmentation.
https://www.leidinger.net/blog/2024/05/07/plotting-the-freebsd-memory-fragmentation/
My goal was not comparing a specific change on a given
reebsd.org/D40575 to
be committed?
Maybe some other people want to have a look at the memory fragmentation
and some of Bojans work
(https://wiki.freebsd.org/SummerOfCode2023Projects/PhysicalMemoryAntiFragmentationMechanisms).
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinge
server
from poudriere somewhere.
What I noticed (except that printing the new CAP stuff for non-CAP
enabled processes by default is disturbing) is, that compat11 stuff is
called (seems the rust ecosystem is not keeping up with our speed of
development...). Not sure if it matters here that some
but it's only a metric to quantify memory fragmentation.
Any ideas how to track this down more easily than running the entire
poudriere in ktrace (e.g. a hint/script which dtrace probes to use)?
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
Am 2024-03-29 18:21, schrieb Alexander Leidinger:
Am 2024-03-29 18:13, schrieb Mark Johnston:
On Fri, Mar 29, 2024 at 04:52:55PM +0100, Alexander Leidinger wrote:
Hi,
sources from 2024-03-11 work. Sources from 2024-03-25 and today don't
work
(see below for the issue). As the mo
Am 2024-03-29 18:13, schrieb Mark Johnston:
On Fri, Mar 29, 2024 at 04:52:55PM +0100, Alexander Leidinger wrote:
Hi,
sources from 2024-03-11 work. Sources from 2024-03-25 and today don't
work
(see below for the issue). As the monthly stabilisation pass didn't
find
obvious iss
w, ccache, retpoline active)
- try a world without bind_now, retpoline, CTF, CPUFLAGS, COPTFLAGS
If anyone has an idea how to debug this in some other way...
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@fr
absolutely not important things,
like
this nullfs "cache" option.
In long term, we would have to export nmount(2) strings since bits in
flags are finite, but I prefer to delay it as much as possible.
Why do you want to delay this? Personal priorities, or technical
reasons?
Bye,
Alexander
Am 2024-03-09 15:27, schrieb Rick Macklem:
On Sat, Mar 9, 2024 at 5:08 AM Alexander Leidinger
wrote:
Am 2024-03-09 06:07, schrieb Warner Losh:
> On Thu, Mar 7, 2024 at 1:05 PM Jamie Landeg-Jones
> wrote:
>
>> Alexander Leidinger wrote:
>>
>>> Hi,
>>>
Am 2024-03-09 06:07, schrieb Warner Losh:
On Thu, Mar 7, 2024 at 1:05 PM Jamie Landeg-Jones
wrote:
Alexander Leidinger wrote:
Hi,
what is the reason why "nocache" is not displayed in the output of
"mount" for nullfs options?
Good catch. I also notice that "hi
che. Based on this
experience, I'm confident that applying nocache works as expected in
your scenario as well.
It does. The question is how to I _see_ that a mount point is _setup_
with nocache? In the above example the FS _is_ mounted with nocache, but
it is _not displayed_ i
g the source I wanted to do it more
quickly by looking at the mount options.
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
signature.asc
Description: OpenPGP digital signature
On 04.03.2024 15:33, Jakob Alvermark wrote:
On 3/4/24 21:13, Alexander Motin wrote:
On 04.03.2024 15:00, Poul-Henning Kamp wrote:
Nov 30 03:23:18 7950X3D-UFS kernel: ue0: link state changed to DOWN
Nov 30 03:23:18 7950X3D-UFS kernel: ue0: link state changed to UP
Nov 30 03:23:18 7950X3D-UFS
ld be good to
understand what's wrong is there exactly, since IMHO it is a big problem
now. Unfortunately HPS was unable to reproduce it on his laptop (that
makes me wonder if is is specific to chipset(s) or thunderbolt?), so it
ended nowhere so far.
--
Alexander Motin
).
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
signature.asc
Description: OpenPGP digital signature
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
signature.asc
Description: OpenPGP digital signature
Am 2024-02-13 01:58, schrieb Konstantin Belousov:
On Mon, Feb 12, 2024 at 11:54:02AM +0200, Konstantin Belousov wrote:
On Mon, Feb 12, 2024 at 10:35:56AM +0100, Alexander Leidinger wrote:
> Hi,
>
> dovecot (and no other program I use on this machine... at least not that I
> notice i
info available.
Backtrace stopped: Cannot access memory at address 0x3af13a225ab8
---snip---
Any ideas?
Due to another issue in userland, I updated to 2024-02-11-212006, but I
have the above mentioned version and core still in a BE if needed.
Bye,
Alexander.
ed01153270) at rtld.c:4541:8
frame #56: 0x4d3dfa2a6673
ld-elf.so.1`get_program_var_addr(name=,
lockstate=0x1ded0f98cb80) at rtld.c:4483:9
---snip---
Bye,
Alexander.
after that consensus falls away.
Mike's idea is one that I can get behind since it elegantly solves the
general problem.
+1
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
ve] (4.0G)
8388576 32- free - (16K)
What are you using cyl/hd/sec values for on a system which runs FreeBSD
current or on which you would have to use FreeBSD-current in case of a
repair need? What is the disk hardware on those systems that you still
need cyl/hd/sec
ask the user at install time, and existing systems shall be
handled by those which administrate them (don't touch an existing fstab;
changing the default in the automounter config for a .0 release would be
OK in my opinion, for a .x release in the middle of a stable branch I
would add a commented out noatime option to make it visible but not
active).
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
signature.asc
Description: OpenPGP digital signature
n that way since day one of zfs support
in bsdinstall.
Which I don't mind, as this is what I use anyway. But the correct way
would be to let the user decide.
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgne
etting of bsdinstall should be
for this option).
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
signature.asc
Description: OpenPGP digital signature
John,
On 04.01.2024 09:20, John Kennedy wrote:
On Tue, Jan 02, 2024 at 08:02:04PM -0800, John Kennedy wrote:
On Tue, Jan 02, 2024 at 05:51:32PM -0500, Alexander Motin wrote:
On 01.01.2024 08:59, John Kennedy wrote:
...
My poudriere build did eventually fail as well
b.com/openzfs/zfs/pull/15732 .
--
Alexander Motin
g and then move back to the original place. I would
also assume original log files are not affected, and only files which
were copied (installworld or installkernel or backup files or manual
copies or port install (not sure about pkg install)) are possible
targets.
Bye,
Alexander.
--
ff, I would suggest to try:
- remove auto linklocal from tap0 (like for alc0)
- add auto linklocal to bridge0
If this doesn't help, there is the sysctl
net.inet6.icmp6.nd6_onlink_ns_rfc4861 which you could try to set to 1.
Please read
https://www.freebsd.org/security/advisories/FreeBSD-
oning is vfs.zfs.bclone_enabled.
To check if a pool has made use of block cloning:
zpool get all poolname | grep bclone
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2
Hi,
for my work on service jails (https://reviews.freebsd.org/D40370) I try
to find out what opensm is. On my amd64 system I don't have a man page
nor the binary (and man.freebsd.org doesn't know either about opensm).
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinge
vfs.zfs.dmu_offset_next_sync=0 (loader.conf / sysctl.conf) for the
moment.
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
signature.asc
Description: OpenPGP digital signature
t purpose, then
transferring to the production vm?
Copy the kernel which was build according to the acticle from klara
systems to your target VM.
Would it be expected to work on arm64?
Yes (I use it on an ampere VM in the cloud).
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@lei
On 14.11.2023 12:44, Alexander Motin wrote:
On 14.11.2023 12:39, Mateusz Guzik wrote:
One of the vnodes is probably not zfs, I suspect this will do it
(untested):
diff --git a/sys/contrib/openzfs/module/os/freebsd/zfs/zfs_vnops_os.c
b/sys/contrib/openzfs/module/os/freebsd/zfs/zfs_vnops_os.c
ange(invp, inoffp, outvp,
outoffp, lenp, flags, incred, outcred, fsize_td);
--
Alexander Motin
r, [x19, #768]
db>
I'll keep the debugger open for a while. Can I type something for
additional info?
Regards,
Ronald.
--
Alexander Motin
it was part of configure, then you would have to do the
configure run and check the messages if it generates similar coredumps)
look, which of the 4 poudriere engines were running at this time?
I'd like to rerun/reproduce the package again.
Bye,
Alexander.
--
http://www.Leidin
Am 2023-10-13 17:42, schrieb Dag-Erling Smørgrav:
Alexander Leidinger writes:
some change around certctl (world from 2023-10-09) has broken the
poudriere jail update command. The complete install finishes, certctl
is run, and then there is an exit code 1. This is because I have some
certs
/usr_src
1 error
make[1]: stopped in /space/system/usr_src
make: stopped in /usr/src
[00:01:32] Error: Failed to 'make installworld'
---snip---
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PG
/subDS2
A shallow clone is only taking zop0/ROOT/main-CA72 into account, while a
-r clone is also cloning subDS1 and subDS2.
So as Kyle said, your (and my) use case are not affected by this.
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http
print m
$4 = (EVP_MD_CTX *) 0x43e31de4bc60
(gdb) print *m
$5 = {reqdigest = 0x17e678afd470, digest = 0x0, engine = 0x0, flags = 0,
md_data = 0x0, pctx = 0x0, update = 0x0, algctx = 0x0, fetched_digest =
0x0}
(gdb)
---snip---
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net
On 18.09.2023 19:21, Mark Millard wrote:
On Sep 18, 2023, at 15:51, Mark Millard wrote:
Alexander Motin wrote on
Date: Mon, 18 Sep 2023 13:26:56 UTC :
block_cloning feature is marked as READONLY_COMPAT. It should not
require any special handling from the boot code.
From stand/libsa/zfs
On 16. 9. 2023 19:14, Alexander Motin wrote:
On 16.09.2023 01:25, Graham Perrin wrote:
On 16/09/2023 01:28, Glen Barber wrote:
o A fix for the ZFS block_cloning feature has been implemented.
Thanks
I see
<https://github.com/openzfs/zfs/commit/5cc1876f14f90430b24f1ad2f231de936691940f>,
with
&
es
not even exist anywhere outside of FreeBSD base tree, I'd propose to
give this code another try here too. I see no point to have it disabled
at least in main unless somebody needs time to run some specific tests
first.
--
Alexander Motin
d). IF you have a read-once workload, nothing of this will help. So
all depends on your workload.
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
signature.asc
Description: OpenP
Am 2023-09-04 14:26, schrieb Mateusz Guzik:
On 9/4/23, Alexander Leidinger wrote:
Am 2023-08-28 22:33, schrieb Alexander Leidinger:
Am 2023-08-22 18:59, schrieb Mateusz Guzik:
On 8/22/23, Alexander Leidinger wrote:
Am 2023-08-21 10:53, schrieb Konstantin Belousov:
On Mon, Aug 21, 2023 at
go with the robustness principle, "be liberal what you
accept, but strict in what you provide" = memcmp() should behave
as if it is supported.
Bye,
Alexander.
--
http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF
signature.asc
Description: OpenPGP digital signature
On 09.09.2023 12:32, Mark Millard wrote:
On Sep 8, 2023, at 21:54, Mark Millard wrote:
On Sep 8, 2023, at 18:19, Mark Millard wrote:
On Sep 8, 2023, at 17:03, Mark Millard wrote:
On Sep 8, 2023, at 15:30, Martin Matuska wrote:
On 9. 9. 2023 0:09, Alexander Motin wrote:
Thank you, Martin
as able to reproduce the issue with your script
and found the cause.
I first though the issue is triggered by the `cp`, but it appeared to be
triggered by `cat`. It also got copy_file_range() support, but later
than `cp`. That is probably why it slipped through testing. This patch
fixes it for me: https://github.com/openzfs/zfs/pull/15251 .
Mark, could you please try the patch?
--
Alexander Motin
the issue. I responded to the commit
email only because it makes no difference while vfs.zfs.bclone_enabled is 0.
That in turns means that someone may come up with some
other change for me to test by the time I get around to
setting up another test. Let me know if so.
--
Alexander Motin
Am 2023-09-03 21:22, schrieb Alexander Leidinger:
Am 2023-09-02 16:56, schrieb Mateusz Guzik:
On 8/20/23, Alexander Leidinger wrote:
Hi,
sysctl kern.maxvnodes=1048576000 results in 100% CPU and a
non-killable
sysctl program. This is somewhat unexpected...
fixed here
https
1 - 100 of 2153 matches
Mail list logo
