Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Carlos E.R." Newsgroups: alt.os.linux.mint,comp.os.linux.networking Subject: Re: very odd nfs behaviour Date: Fri, 24 Jan 2025 22:56:30 +0100 Lines: 16 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net QU38SjJmjUZ36TIY41LS8gwSKCQkWmRHufelZum3EcSnq9phlu X-Orig-Path: Telcontar.valinor!not-for-mail Cancel-Lock: sha1:THandacodkEJ4pn4PPYNFLV11UQ= sha256:nZY4ymIC4pzjKQ3H4yQ5oSx6oANWhwJarVjod0tZZhY= User-Agent: Mozilla Thunderbird Content-Language: es-ES, en-CA In-Reply-To: Xref: csiph.com alt.os.linux.mint:43934 comp.os.linux.networking:8531 On 2025-01-24 17:56, Mike Scott wrote: > A very odd situation here. > > I have a (freebsd) server serving a tree of photos and information > files. It's large, and the paths quite long - whether that's relevant I > don't know. If you are using nfs version 3, perhaps try version 4. If version 4, what's in the exports file? All client machines have the same fstab nfs entry? -- Cheers, Carlos.