https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277389
--- Comment #34 from Mark Millard ---
FYI:
With vfs.nullfs.cache_vnodes=0 I instead got the
"failed to reclaim memory" type of failure, losing
control because of what had been killed.
So the nullfs VNODE caching is not a fundamental
part
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277389
--- Comment #33 from Mark Millard ---
(In reply to Mark Millard from comment #32)
FYI:
This is still with the very simple zpool type: a
single GPT partition on just one physical drive.
No other zpool present.
The drive was attached via U
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277389
--- Comment #32 from Mark Millard ---
(In reply to Mark Millard from comment #31)
The console output's backtrace:
panic: pmap_growkernel: no memory to grow kernel
cpuid = 6
time = 1710740968
KDB: stack backtrace:
db_trace_self() at db_tra
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277389
--- Comment #31 from Mark Millard ---
(In reply to Mark Millard from comment #30)
The vmstat -z output:
vmstat -z
ITEM SIZE LIMIT USED FREE REQ FAIL SLEEP XDOM
UMA Kegs: 512, 0, 92
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277389
--- Comment #30 from Mark Millard ---
The dump worked. The backtrace related part of core.txt.0
follows. The system was booted from a PkgBase kernel and
world for the test, not from a personal build.
# less /var/crash/core.txt.0
aarch64-m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277389
--- Comment #29 from Mark Millard ---
On an aarch64 with 32 GiBytes of RAM (noswap enabled)
I got a panic:
panic: pmap_growkernel: no memory to grow kernel
So, I'd say: Reproduced.
I'll note that I rebooted between the iozone write
step
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
Bug ID: 21
Summary: ice driver report I2C error messages of E822 copper
LAN ports
Product: Base System
Version: 14.0-RELEASE
Hardware: amd64
OS: A
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277389
--- Comment #28 from pascal.guitier...@gmail.com ---
(In reply to Mark Millard from comment #27)
i've tried using a -stable kernel (FreeBSD 14.0-STABLE #0
stable/14-n266971-91c1c36102a6: Thu Mar 14 04:49:15 UTC 2024), same result.
command
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277389
--- Comment #27 from Mark Millard ---
(In reply to pascal.guitierrez from comment #26)
I'll note that I never used mount_nullfs explicitly at
any point but I still got the huge difference in VNODE
results in "vmstat -z" when doing your tes
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277389
--- Comment #26 from pascal.guitier...@gmail.com ---
(In reply to Mark Millard from comment #24)
Hi Mark,
I can try with those settings and on -stable, however I'm not using nullfs in
my tests so those loader settings won't have any effect
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277740
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|f...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277764
Bug ID: 277764
Summary: daemon(8): high CPU usage after stopping and
continuing child process
Product: Base System
Version: CURRENT
Hardware: Any
OS:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277389
--- Comment #25 from Mark Millard ---
(In reply to Mark Millard from comment #23)
22941Mi Wired looks to be where it finally stabilized while
the system was left idle. The later decrements that I happened
to watch were in smaller sized chu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231574
--- Comment #2 from Chris Davidson ---
After a little further pondering and some feedback, this may be something that
can be defined to be more clear and concise.
The examples section of a manual page is suppose to help guide the person,
h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277506
Ed Maste changed:
What|Removed |Added
CC||cperc...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277655
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277740
--- Comment #1 from Ed Maste ---
> It should emit a warning or make multiple copies of the linked file.
IMO it should do both - create copies of the file for correctness, and emit a
warning for the undesired size increase.
--
You are rec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277760
Bug ID: 277760
Summary: sh: cd prints path when prefixed with ./
Product: Base System
Version: Unspecified
Hardware: Any
OS: Any
Status: New
Severit
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271551
Anton Saietskii changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277389
--- Comment #24 from Mark Millard ---
(In reply to pascal.guitierrez from comment #11)
If you can test main , stable/14 , or stable/13 , then
testing with:
nullfs_load="YES"
vfs.nullfs.cache_vnodes=0
zfs_load="YES"
in /boot/loader.conf c
21 matches
Mail list logo
