Path: csiph.com!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Mike Scott Newsgroups: alt.os.linux.mint,comp.os.linux.networking,comp.unix.bsd.freebsd.misc Subject: (resolved) Re: very odd nfs behaviour Date: Mon, 27 Jan 2025 15:41:37 +0000 Organization: Scott family Lines: 54 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Mon, 27 Jan 2025 16:41:38 +0100 (CET) Injection-Info: dont-email.me; posting-host="67b0c38c26adba2195ee8efaac8672ee"; logging-data="1063464"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX192Z9leHTPQ7eyGBGarU4dqrRas7fjSucw=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:3KTH/auBThXP5bKnPYMfnCH+xhE= Content-Language: en-GB In-Reply-To: Xref: csiph.com alt.os.linux.mint:43961 comp.os.linux.networking:8538 comp.unix.bsd.freebsd.misc:4154 [ comp.unix.bsd.freebsd.misc added ] On 24/01/2025 17:55, Richard Kettlewell wrote: > Mike Scott writes: >> 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. > [ screed about file names being truncated when read over nfs ] ....... >> >> I'm at a loss! Can anyone suggest what's going on here please? I'm >> sure this used to work! > > Formerly, Linux NFS servers could get confused by large directories. > https://lwn.net/Articles/544520/ is the best writeup I’ve found. > > In your case the server is FreeBSD, so Linux’s historical bugs aren’t > directly relevant, beyond highlighting that merely listing a directory > is more complex than you might initially imagine. I’m not sure why a > hypothetical similar bug in FreeBSD would only be visible on a subset of > clients either. > OK, I've at least found what's happened, if not the root issue. Sort of mea culpa, for which I apologise. In spite of my assertion (which I should have checked and didn't), the mount options differed. The working machines all specified rsize=8192. My box was using a much larger figure, of 131072 (ie 32 * 4096). It seems anything over 8192 causes this issue - that filenames get truncated. Whether that's a linux client issue or a freebsd server issue, or the result of interworking, I've no idea. Nor can I imagine why it should happen without errors being flagged up somewhere (I checked the logs at both ends) -- which is nasty, because I had a system that met the specs and mostly worked but very occasionally (< about 1 in 100k times, I reckon) failed silently. Ouch. Anyway, thanks to all for comments and advice offered. I'm back 'on the road'; maybe if someone else hits the same issue they'll find this thread. -- Mike Scott Harlow, England