Re: very odd nfs behaviour

From	Grant Taylor <gtaylor@tnetconsulting.net>
Newsgroups	alt.os.linux.mint, comp.os.linux.networking
Subject	Re: very odd nfs behaviour
Date	2025-01-25 20:08 -0600
Organization	TNet Consulting
Message-ID	<vn45e5$qeh$1@tncsrv09.home.tnetconsulting.net> (permalink)
References	<vn0gn0$2ajlc$1@dont-email.me>

Cross-posted to 2 groups.

Show all headers | View raw

On 1/24/25 10:56, Mike Scott wrote:
> A very odd situation here.

Yes, it seems that way.

I don't have an answer, or even a hint.  But I do have some additional 
observations that I didn't see mentioned in the thread:

> 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.

How long is "quite long"?  Are you tickling any sort of limits?

> On two of three machines all running mint at various versions all is 
> well; I have problems on the third, which happens to be my desktop box.

What versions (kernel, OS, etc.) are the three machines?

> An example good listing would be (sorry about wrap):

The line wrap actually came through well on my end.

> mike@troi ~ $ ls /nfs/mmedia/pictures/originals-index4/mike/ 
> camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.*
> /nfs/mmedia/pictures/originals-index4/mike/ 
> camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.exif
> /nfs/mmedia/pictures/originals-index4/mike/ 
> camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--info.html
> /nfs/mmedia/pictures/originals-index4/mike/ 
> camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG.sha
> /nfs/mmedia/pictures/originals-index4/mike/ 
> camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.html
> /nfs/mmedia/pictures/originals-index4/mike/ 
> camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--slide.png
> /nfs/mmedia/pictures/originals-index4/mike/ 
> camera2014/20140531b/2014-04-24/2014-04-15_10-21-47.JPG--thumb.png
> 
> That corresponds exactly to what's on the server.

Okay.

> However, on my desktop m/c, the same command complains about a missing 
> file, and triplicates all the lines bar the first, which is duplicated, 
> and there's an error about not finding a file that has an incorrect name 
> anyway:

This feel like NFS loosing state and or synchronization between the 
client and server when listing directories.

The duplication -> triplication and the wild name seem like something 
has failed somewhere at the underlying RPC layer.

> If I unmount and remount the file system, I get different results - 
> always works on the other machines, and fails /differently/ each time on 
> mine.

Different network / RPC / NFS mismatches would likely happen with 
underlying protocol problems.

> I've also seen this happen in a virtual machine running on my box.

Is the VM running on the same box that has the problem?  Or is it 
running on a different system?

> It happens whether I hard mount or use the automounter.

I'm not surprised by that.  IMHO the auto-mounter's only role is to 
automatically mount (and unmount when idle) the NFS export using 
standard mount methods.

> The OS versions are different - I'm running mint 21.2, the VM is at 
> 21.3; while the others are both rather older versions (and different 
> hardware). The machines are all configured the same.

So not exactly the same versions, but close to each other.

> I'm at a loss! Can anyone suggest what's going on here please? I'm sure 
> this used to work!

I'd reach for a packet capture and feed it into Wireshark or something 
similar that can analyze the underlying UDP / TCP, RPC, and NFS protocol 
and call out any oddities.

-- 
Grant. . . .

Back to comp.os.linux.networking | Previous | Next — Previous in thread | Find similar

Thread

very odd nfs behaviour Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-01-24 16:56 +0000
  Re: very odd nfs behaviour Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-01-24 17:00 +0000
  Re: very odd nfs behaviour Edmund <nomail@hotmail.com> - 2025-01-24 18:01 +0100
    Re: very odd nfs behaviour Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-01-24 17:30 +0000
  Re: very odd nfs behaviour Richard Kettlewell <invalid@invalid.invalid> - 2025-01-24 17:55 +0000
    (resolved) Re: very odd nfs behaviour Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-01-27 15:41 +0000
      Re: (resolved) Re: very odd nfs behaviour Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-27 23:24 +0000
        Re: (resolved) Re: very odd nfs behaviour Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-01-28 08:06 +0000
          Re: (resolved) Re: very odd nfs behaviour "Carlos E.R." <robin_listas@es.invalid> - 2025-01-28 12:34 +0100
          Re: (resolved) Re: very odd nfs behaviour pinnerite <pinnerite@gmail.com> - 2025-01-28 22:58 +0000
  Re: very odd nfs behaviour "Carlos E.R." <robin_listas@es.invalid> - 2025-01-24 22:56 +0100
    Re: very odd nfs behaviour Paul <nospam@needed.invalid> - 2025-01-24 17:34 -0500
      Re: very odd nfs behaviour "Carlos E.R." <robin_listas@es.invalid> - 2025-01-25 01:45 +0100
    Re: very odd nfs behaviour Mike Scott <usenet.16@scottsonline.org.uk.invalid> - 2025-01-25 17:02 +0000
  Re: very odd nfs behaviour "Arti F. Idiot" <addr@is.invalid> - 2025-01-24 17:13 -0700
  Re: very odd nfs behaviour Lawrence D'Oliveiro <ldo@nz.invalid> - 2025-01-26 00:01 +0000
  Re: very odd nfs behaviour Grant Taylor <gtaylor@tnetconsulting.net> - 2025-01-25 20:08 -0600

csiph-web