NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: misc/57286
The following reply was made to PR misc/57286; it has been noted by GNATS.
From: Jim Spath <jspath55%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc:
Subject: Re: misc/57286
Date: Thu, 6 Apr 2023 19:53:46 -0400
I ran additional shell commands to determine why this occurs:
# sysctl -w kern.maxvnodes=2000
sysctl: kern.maxvnodes: Device busy
On one system the current maxvnode count is:
# sysctl -n kern.maxvnodes
402626
Higher values than 2,000 succeed:
# sysctl -w kern.maxvnodes=402625
kern.maxvnodes: 402626 -> 402625
# sysctl -w kern.maxvnodes=100000
kern.maxvnodes: 402625 -> 100000
# sysctl -w kern.maxvnodes=50000
kern.maxvnodes: 100000 -> 50000
# sysctl -w kern.maxvnodes=10000
kern.maxvnodes: 50000 -> 10000
The lower limit for this system is around 4,000.
# sysctl -w kern.maxvnodes=3000
sysctl: kern.maxvnodes: Device busy
# sysctl -w kern.maxvnodes=4000
sysctl: kern.maxvnodes: Device busy
# sysctl -w kern.maxvnodes=4500
kern.maxvnodes: 5000 -> 4500
Could the test determine a valid number of nodes before trying to
lower the value?
Home |
Main Index |
Thread Index |
Old Index