Re: Here's One - NFS - Mounting Over Share = Nada

On 03/04/2025 11:19, c186282 wrote:

On 4/3/25 2:40 AM, Computer Nerd Kev wrote:

Carlos E.R. <robin_listas@es.invalid> wrote:

>
What I do, is use some option that is only valid on version 4,
so I force version 4.

>
There's also the nfsvers=4 option.

    As noted somewhere else, I *do* see NFS4 in etab as
   a filled-in default.
    Also, PRE-filled subdirs under the share are sent to
   the clients properly, including file updates. The issue
   is with re-mounting USB drives OVER empty folders that
   were under the share folder at boot. Doesn't SEE the
   changes, only what was originally there.
    Mounts/re-mounts don't seem THAT unusual in Linux, so
   I'm kinda surprised NFS isn't dealing with it.
    Note external USB drives don't ALWAYS come up in the
   same order ... kinda depends on which order they fully
   init. Even a millisecond determines which will be
   sda, sdb, etc ... gotta name, or tagfile, the drives
   to make sure - Python can most easily find/parse that
   kind of info. But that's NEXT week ....
 

Oh dear. You really haven't grasped this have you?
1. Use fstab to PERMANTLY mount them at boot time before NFS even come up
2. use their partition UUIDs in fstab  to associate  each partition with a defined mount point.
e.g.
PARTUUID=0916c1e1-d006-4b19-9378-d687271d3612  /home               ext4    defau
lts,noatime  0       1
PARTUUID=aec7525a-1e13-4a52-a23f-d8a0d17f6da7  /home/Media ext4
  defaults,noatime  0       1
PARTUUID=778a9e44-03 /backup ext4    defaults,noatime  0       1
PARTUUID=778a9e44-06 /backup2 ext4    defaults,noatime  0       1
PARTUUID=778a9e44-05 /home/Media/Unedited ext4 defaults,noatime  0       1
These are all USB connected SSD partitions. They are all exported by NFS without problems.
--
Renewable energy: Expensive solutions that don't work to a problem that doesn't exist instituted by self legalising protection rackets that don't protect,  masquerading as public servants who don't serve the public.