[Bug 292884] nfsd causes kernel panic
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 292884] nfsd causes kernel panic"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 18 Feb 2026 10:55:44 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292884
--- Comment #23 from Arrigo Triulzi <arrigo@alchemistowl.org> ---
(In reply to Rick Macklem from comment #20)
Sorry, I had missed this question - no, I do not run rpc.lockd.
Answering the questions you asked the other reporter:
* no rpc.lockd
* mount options (no nfsstat -m on OpenBSD):
bora.vmnet:/exports/vmbackups/tempest on /nfs type nfs (nodev, noexec, nosuid,
v3, tcp, timeo=100, retrans=101)
* nfsstat output (system up since installing your patch):
Client Info:
Getattr Setattr Lookup Readlink Read Write Create Remove
9038 6318 63563 0 3761 47087 1577 1587
Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access
1577 0 0 0 0 7390 0 4936
Mknod Fsstat Fsinfo PathConf Commit
0 4 1 0 689
Rpc Info:
TimedOut Invalid X Replies Retries Requests FrcSync
0 0 0 2 147528 0
Cache Info:
Attr Hits Misses Lkup Hits Misses BioR Hits Misses BioW Hits Misses
132679 9038 71257 63563 4054 3761
18446744073709531827 47087
BioRLHits Misses BioD Hits Misses DirE Hits Misses
0 0 0 0 2650 2650
Server Info:
Getattr Setattr Lookup Readlink Read Write Create Remove
0 0 0 0 0 0 0 0
Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access
0 0 0 0 0 0 0 0
Mknod Fsstat Fsinfo PathConf Commit
0 0 0 0 0
Server Ret-Failed
0
Server Faults
0
Server Cache Stats:
Inprog Idem Non-idem Misses
0 0 0 0
Server Write Gathering:
WriteOps WriteRPC Opsaved
0 0 0
* NFS configuration (in /etc/rc.conf.d/nfsd):
nfs_server_enable="YES"
nfs_server_flags="-t"
* Network setup:
bridge2: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric
0 mtu 1500
description: Local VM network - NFS
options=10<VLAN_HWTAGGING>
ether 58:9c:fc:10:43:19
id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
bridge flags=0<>
member: tap8 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
port 24 priority 128 path cost 2000000 vlan protocol 802.1q
member: tap6 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
port 22 priority 128 path cost 2000000 vlan protocol 802.1q
member: tap2 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
port 18 priority 128 path cost 2000000 vlan protocol 802.1q
member: epair2a flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
port 8 priority 128 path cost 2000 vlan protocol 802.1q
groups: bridge local
nd6 options=9<PERFORMNUD,IFDISABLED>
where epair2 is the host machine running NFS and the tap interfaces are the
OpenBSD VMs. The network is on 172.16.255/24, not that it should matter in the
least, with .1 the host and the guests on .2, .3, .4.
This configuration is unchanged as of FreeBSD 14.3-RELEASE, the host was
installed with FreeBSD 14.0-RELEASE when initially procured.
--
You are receiving this mail because:
You are the assignee for the bug.