Date: Tue, 11 Nov 2025 04:12:19 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 275030] buildworld fails if obj dir is NFS-mounted Message-ID: <bug-275030-227-byOebHENXT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-275030-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275030 --- Comment #24 from void@f-m.fm --- (In reply to Rick Macklem from comment #23) Hi Rick The nfs server is nfs v3 It runs a raidz2 pool with sharenfs property on selected vdevs. The OS is 15.0-ALPHA2 stable/15-n280129-deaa609d065d GENERIC amd64 1500064 1500064 It was source built on 14th Sept. The nfs client is on a rpi2b+ running 16:current of 3rd Nov. Does the uarch issue affect nfsv3 as well? Here's nfsstat -m. Thank you for looking at this # nfsstat -m 192.168.1.102:/data/src-rpi2b on /usr/src nfsv3,tcp,resvport,nconnect=1,hard,cto,lockd,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=16,wcommitsize=4194304,timeout=120,retrans=2 192.168.1.102:/data/ccache-rpi2b on /var/cache/ccache nfsv3,tcp,resvport,nconnect=1,hard,cto,lockd,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=16,wcommitsize=4194304,timeout=120,retrans=2 192.168.1.102:/data/ports-rpi2b on /usr/ports nfsv3,tcp,resvport,nconnect=1,hard,cto,lockd,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=16,wcommitsize=4194304,timeout=120,retrans=2 192.168.1.102:/data/obj-rpi2b on /usr/obj nfsv3,tcp,resvport,nconnect=1,hard,cto,lockd,sec=sys,acdirmin=3,acdirmax=60,acregmin=5,acregmax=60,nametimeo=60,negnametimeo=60,rsize=65536,wsize=65536,readdirsize=65536,readahead=16,wcommitsize=4194304,timeout=120,retrans=2 -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-275030-227-byOebHENXT>