Path: ...!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: vallor <vallor@cultnix.org>
Newsgroups: comp.os.linux.misc
Subject: Re: Here's One - NFS - Mounting Over Share = Nada
Date: 2 Apr 2025 11:40:18 GMT
Lines: 70
Message-ID: <m54m11Fhof8U5@mid.individual.net>
References: <UQ-dndQV6amaDnH6nZ2dnZfqnPednZ2d@giganews.com>
	<m54j20Fhof8U3@mid.individual.net> <4qivblx7ff.ln2@Telcontar.valinor>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net VuMV/pkmljzZRjItlaarswr4svkU1eQqnbtLWnx4sWqnkrZ/sj
Cancel-Lock: sha1:knXr8epR6O0eiP5/1uWqvntUlw0= sha256:twzJuyXrxux1y8FKNC09GRUsbNc2gZ1My8tnhtoOzrk=
X-Face: +McU)#<-H?9lTb(Th!zR`EpVrp<0)1p5CmPu.kOscy8LRp_\u`:tW;dxPo./(fCl
 CaKku`)]}.V/"6rISCIDP`
User-Agent: Pan/0.162 (Hmm4; f7d29671; Linux-6.14.0)
Bytes: 3866

On Wed, 2 Apr 2025 13:14:44 +0200, "Carlos E.R." <robin_listas@es.invalid>
wrote in <4qivblx7ff.ln2@Telcontar.valinor>:

> On 2025-04-02 12:49, vallor wrote:
>> On Tue, 1 Apr 2025 21:29:48 -0400, c186282 <c186282@nnada.net> wrote in
>> <UQ-dndQV6amaDnH6nZ2dnZfqnPednZ2d@giganews.com>:
>> 
>>> Here's an interesting problem ....
>>>
>>> I re-mount USB drives onto NFS share points. The problem is that NFS
>>> doesn't SEE that - it only sees the previously empty dir instead.
>>> Add a tag file to that dir and that's ALL you will see in the share on
>>> another PC.
>>>
>>> Tried variations of exportfs ... including the '-r' and '-au' then
>>> '-a' AFTER doing the mount. Sorry, the clients can't see the mount.
>>> The NFS stuff seems to cut in very early - before the USB re-mounts
>>> (done @reboot). If you look on the host machine you DO see the USB
>>> drives, but NEVER over the NFS share.
>>>
>>> Why re-mount the USBs ? Because you can't always rely on Linux to
>>> mount them in the same order, used to be even the same place.
>>> '/media/<user>/whatever' seems hard-wired these days, but with
>>> multiple USB drives you still can't count on drive 1 being the drive 1
>>> in /media/<user>. Kinda depends on which comes online first.
>>> Naming the drives helps, but even then.
>>>
>>> And no, symlinks to some other mount point don't work ... NFS just
>>> shares a link to nowhere on the clients. 'hard' links ???
>>>
>>> Have ONE share that's not a re-mounted anything - THAT always shows
>>> perfectly on the clients. Weird thing, somehow, at one point I DID get
>>> it to work - but not sure HOW. Just commented-out the old NFS and
>>> fstab stuff, so I've been able to re-try, but now none work. Set
>>> everything to 775 or 777 for development work, but that doesn't help.
>>>
>>> SAMBA - this sort of thing works fine, but I've had horrible probs
>>> with SAMBA with the latest distros, ALWAYS intractable permissions
>>> issues no matter the tweaks, hence using NFS.
>>>
>>> So ... any insights on how to get NFS to "see" whatever IS mounted to
>>> the share point AT THE MOMENT ???
>>>
>>> Oh, latest MX Linux.
>> 
>> Take a look at "man exports" under the "nohide" option.
> 
> Ah, yes.
> 
> Last line says "not if you use NFSv4". The hiding doesn't happen with
> version 4.
> 
> Reminds me of something. How does one know what version is actually
> used?

use "mount | grep mountpoint", the version will be in there as "vers=",
and also the type, e.g.:

$ mount | grep /nfs/ds
192.168.23.12:/volume1/ds on /nfs/ds type nfs4
(rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,
hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.23.254,
local_lock=none,addr=192.168.23.12)

(I've wrapped the line for posting on Usenet.)

-- 
-v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
   OS: Linux 6.14.0 Release: Mint 22.1 Mem: 258G
   "The world is so big and so global now."