On 2025-04-02 03:29, c186282 wrote:
So ... any insights on how to get NFS to
"see" whatever IS mounted to the share point
AT THE MOMENT ???
Restart NFS manually after the manual mount of external media.
Or, define the usb mounts in fstab, and exports. But then, you can not
boot without the usb media.
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.
On Tue, 1 Apr 2025 21:29:48 -0400, c186282 <[email protected]> wrote in <[email protected]>:
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.
On Tue, 1 Apr 2025 21:29:48 -0400, c186282 <[email protected]> wrote in <[email protected]>:
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.
On 2025-04-02 12:49, vallor wrote:
On Tue, 1 Apr 2025 21:29:48 -0400, c186282 <[email protected]> wrote in
<[email protected]>:
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?
On 02/04/2025 11:35, Carlos E.R. wrote:
On 2025-04-02 03:29, c186282 wrote:I missed the earlier part, but mount | grep nfs...shows what is mounted
So ... any insights on how to get NFS to
"see" whatever IS mounted to the share point
AT THE MOMENT ???
Restart NFS manually after the manual mount of external media.
Or, define the usb mounts in fstab, and exports. But then, you can not
boot without the usb media.
or mount | grep mount-point...
On 2025-04-02 12:49, vallor wrote:
On Tue, 1 Apr 2025 21:29:48 -0400, c186282 <[email protected]> wrote in
<[email protected]>:
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?
On Wed, 2 Apr 2025 13:14:44 +0200, "Carlos E.R." <[email protected]d> wrote in <[email protected]r>:
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.)
On Wed, 2 Apr 2025 13:14:44 +0200, "Carlos E.R." <[email protected]d> wrote in <[email protected]r>:
On 2025-04-02 12:49, vallor wrote:
On Tue, 1 Apr 2025 21:29:48 -0400, c186282 <[email protected]> wrote in
<[email protected]>:
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.)
On 4/2/25 7:14 AM, Carlos E.R. wrote:
On 2025-04-02 12:49, vallor wrote:
On Tue, 1 Apr 2025 21:29:48 -0400, c186282 <[email protected]> wrote in
<[email protected]>:
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?
/var/libs/nfs/etab reads "NFS4"
But remounts to the shared dir still do
not register.
I'd LIKE NFS to reflect WHATEVER THE HELL I currently
have mounted to that share dir.
Or maybe it just CAN'T ??? There ARE reasons I stuck
with SAMBA so long ... it (used to) Just Work.
Simple goal - I want NFS to share what's mounted
to the stated point ALL THE TIME, not JUST five
microseconds after boot-up. MAY want scripts to
change what's mounted there a number of times
per day for max flexibility.
CAN NFS *do* that without horrific complications ?
On 2025-04-02 13:39, c186282 wrote:
On 4/2/25 7:14 AM, Carlos E.R. wrote:
On 2025-04-02 12:49, vallor wrote:
On Tue, 1 Apr 2025 21:29:48 -0400, c186282 <[email protected]> wrote in >>>> <[email protected]>:
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?
/var/libs/nfs/etab reads "NFS4"
No such file here, not even the directory. It is "/var/lib/nfs/etab" here.
But no, the version is not there:
/data/hoard_1
192.168.2.0/24(rw,sync,wdelay,hide,nocrossmnt,secure,no_root_squash,no_all_squash,subtree_check,secure_locks,acl,no_pnfs,fsid=10,anonuid=65534,anongid=65534,sec=sys,rw,secure,no_root_squash,no_all_squash)
But remounts to the shared dir still do
not register.
I'd LIKE NFS to reflect WHATEVER THE HELL I currently
have mounted to that share dir.
Or maybe it just CAN'T ??? There ARE reasons I stuck
with SAMBA so long ... it (used to) Just Work.
As I said, I restart the server. Or perhaps, "exportfs -r".
Actually, I have a server machine with external disks, and they are just mounted and exported properly, no issues.
Except that if the disk is not mounted, nfs doesn't start.
On 4/2/25 8:19 AM, Carlos E.R. wrote:
On 2025-04-02 13:39, c186282 wrote:
On 4/2/25 7:14 AM, Carlos E.R. wrote:
On 2025-04-02 12:49, vallor wrote:
On Tue, 1 Apr 2025 21:29:48 -0400, c186282 <[email protected]>
wrote in
<[email protected]>:
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?
/var/libs/nfs/etab reads "NFS4"
No such file here, not even the directory. It is "/var/lib/nfs/etab"
here.
But no, the version is not there:
/data/hoard_1
You FIRST have to set up NFS and then edit /etc/exports and
finally "exportfs -a". THEN the file will be in var/libs/nfs.
That's what NFS really uses.
192.168.2.0/24(rw,sync,wdelay,hide,nocrossmnt,secure,no_root_squash,no_all_squash,subtree_check,secure_locks,acl,no_pnfs,fsid=10,anonuid=65534,anongid=65534,sec=sys,rw,secure,no_root_squash,no_all_squash)
But remounts to the shared dir still do
not register.
I'd LIKE NFS to reflect WHATEVER THE HELL I currently
have mounted to that share dir.
Or maybe it just CAN'T ??? There ARE reasons I stuck
with SAMBA so long ... it (used to) Just Work.
As I said, I restart the server. Or perhaps, "exportfs -r".
Sorry, restarts do NOT work.
On 2025-04-02 12:48, The Natural Philosopher wrote:
On 02/04/2025 11:35, Carlos E.R. wrote:
On 2025-04-02 03:29, c186282 wrote:I missed the earlier part, but mount | grep nfs...shows what is mounted
So ... any insights on how to get NFS to
"see" whatever IS mounted to the share point
AT THE MOMENT ???
Restart NFS manually after the manual mount of external media.
Or, define the usb mounts in fstab, and exports. But then, you can
not boot without the usb media.
or mount | grep mount-point...
The point he syas is that when exporting "/media/<user>/usbsomething",
the clients can not see the files, only the mount point.
So ... any insights on how to get NFS to
"see" whatever IS mounted to the share point
AT THE MOMENT ???
What I do, is use some option that is only valid on version 4,
so I force version 4.
On 02/04/2025 12:18, Carlos E.R. wrote:
On 2025-04-02 12:48, The Natural Philosopher wrote:So he is trying to export a mounted partition?
On 02/04/2025 11:35, Carlos E.R. wrote:
On 2025-04-02 03:29, c186282 wrote:I missed the earlier part, but mount | grep nfs...shows what is mounted
So ... any insights on how to get NFS to
"see" whatever IS mounted to the share point
AT THE MOMENT ???
Restart NFS manually after the manual mount of external media.
Or, define the usb mounts in fstab, and exports. But then, you can
not boot without the usb media.
or mount | grep mount-point...
The point he syas is that when exporting "/media/<user>/usbsomething",
the clients can not see the files, only the mount point.
I always start with ...
*(ro,sync,no_root_squash,no_subtree_check)
In /etc/exports for the least restricted export
On 4/2/25 1:04 PM, The Natural Philosopher wrote:
On 02/04/2025 12:18, Carlos E.R. wrote:
On 2025-04-02 12:48, The Natural Philosopher wrote:So he is trying to export a mounted partition?
On 02/04/2025 11:35, Carlos E.R. wrote:
On 2025-04-02 03:29, c186282 wrote:I missed the earlier part, but mount | grep nfs...shows what is mounted >>>>
So ... any insights on how to get NFS to
"see" whatever IS mounted to the share point
AT THE MOMENT ???
Restart NFS manually after the manual mount of external media.
Or, define the usb mounts in fstab, and exports. But then, you can
not boot without the usb media.
or mount | grep mount-point...
The point he syas is that when exporting
"/media/<user>/usbsomething", the clients can not see the files, only
the mount point.
I always start with ...
*(ro,sync,no_root_squash,no_subtree_check)
In /etc/exports for the least restricted export
Ok, tried your param list ... but still nada on
the later-login mounts. Exportfs adds a bunch of
other defaults to etab.
It's VERY annoying.
As best I can tell, NFS cuts in VERY early and there
is no sane way to stop/delay it. As such it ONLY sees
the original, empty, folder we are later gonna
remount the USBs to.
Have a 4-drive external USB fixture. The drives USUALLY
come up in order, but experience sez they won't ALWAYS
do that. Depends on how quick the drives initialize,
and there's one magnetic in the mix. sda/sdb/etc may
not ALWAYS, reliably, be the same physical drives.
A Python script can more easily probe/parse info that
can individually identify, that's the next stage.
Anyway, the drives (sometimes) come up in /media/<user>
and I have a mount statement that mounts them in my
NFS share dir, under the appropriate sub-folder.
BUT, NFS just doesn't SEE that - only what was there
(nothing) a microsec after the system boots. Have NOT
been able to use exportfs to change that no matter
the params.
It's vexing - I want to use the USB cluster as NAS
yet this behavior is in the way. BTW there can also
be other, more interesting, uses to being able to
mount/umount/remount different USB drives and such
in a dynamic manner ... maybe soon.
Have a crontab now that tries to remount the USBs
to the NAS folders every 5 minutes. Doesn't help.
Anyway, not sure NFS can *do* what I need it to do.
It's great at sharing pre-existing pre-stuffed
subdirs - have security cam backups going there -
but so far just WON'T handle later mount statements.
As said somewhere, have had horrible probs with SAMBA
in the latest distros - all the online advice and past
experience do NOT get around permissions issues. You
can see the SAMBA share is *there*, just not log on.
They CHANGED something recently and it's ill-documented.
SAMBA *can* cope with the to-the-second mounts, have
used it that way before, even INTERNALLY on a NAS
box so backup pgms would work easily.
Carlos E.R. <[email protected]d> 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.
On 4/3/25 2:40 AM, Computer Nerd Kev wrote:
Carlos E.R. <[email protected]d> 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 ....
On 03/04/2025 11:19, c186282 wrote:
On 4/3/25 2:40 AM, Computer Nerd Kev wrote:Oh dear. You really haven't grasped this have you?
Carlos E.R. <[email protected]d> 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 ....
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.
On 4/3/25 7:03 AM, The Natural Philosopher wrote:
On 03/04/2025 11:19, c186282 wrote:
On 4/3/25 2:40 AM, Computer Nerd Kev wrote:Oh dear. You really haven't grasped this have you?
Carlos E.R. <[email protected]d> 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 ....
Clearly not ... enlighten me ......
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.
Hmmm ...
Haven't used fstab for external USBs in a long time,
but it's worth a TRY here. I'll use the _netdev option
to help cope with any delays.
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.
Gimme a few hours and I'll report.
Oh, I generally mount-by-label, not UUID, since the
label TELLS you stuff.
On 4/2/25 1:04 PM, The Natural Philosopher wrote:
On 02/04/2025 12:18, Carlos E.R. wrote:
On 2025-04-02 12:48, The Natural Philosopher wrote:
I always start with ...
*(ro,sync,no_root_squash,no_subtree_check)
In /etc/exports for the least restricted export
Ok, tried your param list ... but still nada on
the later-login mounts. Exportfs adds a bunch of
other defaults to etab.
It's VERY annoying.
As best I can tell, NFS cuts in VERY early and there
is no sane way to stop/delay it. As such it ONLY sees
the original, empty, folder we are later gonna
remount the USBs to.
Have a 4-drive external USB fixture. The drives USUALLY
come up in order, but experience sez they won't ALWAYS
do that. Depends on how quick the drives initialize,
and there's one magnetic in the mix. sda/sdb/etc may
not ALWAYS, reliably, be the same physical drives.
A Python script can more easily probe/parse info that
can individually identify, that's the next stage.
Anyway, the drives (sometimes) come up in /media/<user>
and I have a mount statement that mounts them in my
NFS share dir, under the appropriate sub-folder.
On 2025-04-03 11:51, c186282 wrote:
On 4/2/25 1:04 PM, The Natural Philosopher wrote:
On 02/04/2025 12:18, Carlos E.R. wrote:
On 2025-04-02 12:48, The Natural Philosopher wrote:
I always start with ...
*(ro,sync,no_root_squash,no_subtree_check)
In /etc/exports for the least restricted export
Ok, tried your param list ... but still nada on
the later-login mounts. Exportfs adds a bunch of
other defaults to etab.
It's VERY annoying.
As best I can tell, NFS cuts in VERY early and there
is no sane way to stop/delay it. As such it ONLY sees
the original, empty, folder we are later gonna
remount the USBs to.
It is working fine for me. You need "nohide" or version 4.
Have a 4-drive external USB fixture. The drives USUALLY
come up in order, but experience sez they won't ALWAYS
do that. Depends on how quick the drives initialize,
and there's one magnetic in the mix. sda/sdb/etc may
not ALWAYS, reliably, be the same physical drives.
A Python script can more easily probe/parse info that
can individually identify, that's the next stage.
So, do not use sda/sdb. Use persistent naming.
Anyway, the drives (sometimes) come up in /media/<user>
and I have a mount statement that mounts them in my
NFS share dir, under the appropriate sub-folder.
Define them in fstab.
On 4/3/25 8:07 AM, Carlos E.R. wrote:
On 2025-04-03 11:51, c186282 wrote:
On 4/2/25 1:04 PM, The Natural Philosopher wrote:
On 02/04/2025 12:18, Carlos E.R. wrote:
On 2025-04-02 12:48, The Natural Philosopher wrote:
I always start with ...
*(ro,sync,no_root_squash,no_subtree_check)
In /etc/exports for the least restricted export
Ok, tried your param list ... but still nada on
the later-login mounts. Exportfs adds a bunch of
other defaults to etab.
It's VERY annoying.
As best I can tell, NFS cuts in VERY early and there
is no sane way to stop/delay it. As such it ONLY sees
the original, empty, folder we are later gonna
remount the USBs to.
It is working fine for me. You need "nohide" or version 4.
Have a 4-drive external USB fixture. The drives USUALLY
come up in order, but experience sez they won't ALWAYS
do that. Depends on how quick the drives initialize,
and there's one magnetic in the mix. sda/sdb/etc may
not ALWAYS, reliably, be the same physical drives.
A Python script can more easily probe/parse info that
can individually identify, that's the next stage.
So, do not use sda/sdb. Use persistent naming.
Anyway, the drives (sometimes) come up in /media/<user>
and I have a mount statement that mounts them in my
NFS share dir, under the appropriate sub-folder.
Define them in fstab.
For you and rbowman ...
Here's what my boxes look like now :
. . . . .
server
/etc/exports :
/home/nas/shar 192.168.0.0/24(rw,sync,no_root_squash,no_subtree_check)
/etc/fstab :
LABEL=ustor1 /home/nas/shar/qshar1 ext4 defaults,_netdev 0 0
LABEL=ustor2 /home/nas/shar/qshar2 ext4 defaults,_netdev 0 0
client
/etc/fstab :
192.168.0.121:/home/nas/shar /mnt/shar nfs defaults, timeo=900,retrans=5,_netdev 0 0
. . . . .
Results - ON the server you can see both of the USB drives,
so they ARE mounting where instructed. There is also a
third subfolder under /shar that's directly written to by
a script on the server box.
On the CLIENT ... you can read/write to that third folder
just fine. However the other two, the shares of the USB
drives mounted on the server to, /home/nas/shar/qshar1 and
/home/nas/shar/qshar2, are just BLANK.
All permissions, server and client, are very generous
for testing purposes - could restrict a bit later.
MAY try sharing each folder under /shar individually
rather that trying to share just /shar and hoping
everything under it gets carried over - which it doesn't.
* c186282 <[email protected]>
| Here's what my boxes look like now :
| server
| /etc/exports :
| /home/nas/shar 192.168.0.0/24(rw,sync,no_root_squash,no_subtree_check)
|
Haven't followed this thread from the beginning, so maybe you've been
there before:
https://www.baeldung.com/linux/nfs-shares-export-import
basically says:
- you need to export both, the mount point /home/nas/shar
*AND* the mounted USB-filesystems /home/nas/shar/qshar[12]
- use crossmnt on /home/nas/shar in /etc/exports to un-hide the
USB-filesystems
HTH
R'
On 03/04/2025 16:27, c186282 wrote:
On 4/3/25 8:07 AM, Carlos E.R. wrote:
On 2025-04-03 11:51, c186282 wrote:
Ahh. You need to add the 'crossmnt' directive to the servers /etc/
exports file for the whatever it is you are mounting
Then it will work the way you want it to
On 2025-04-03 19:08, The Natural Philosopher wrote:
On 03/04/2025 16:27, c186282 wrote:
On 4/3/25 8:07 AM, Carlos E.R. wrote:
On 2025-04-03 11:51, c186282 wrote:
Ahh. You need to add the 'crossmnt' directive to the servers /etc/
exports file for the whatever it is you are mounting
Then it will work the way you want it to
Right, because he is trying to export the parent directory. I export the mount points directly.
crossmnt
This option is similar to nohide but it
makes it possible for clients to access
all filesystems mounted on a filesystem
marked with crossmnt. Thus when a child
filesystem "B" is mounted on a parent
"A", setting crossmnt on "A" has a simi-
lar effect to setting "nohide" on B.
With nohide the child filesystem needs
to be explicitly exported. With
crossmnt it need not. If a child of a
crossmnt file is not explicitly ex-
ported, then it will be implicitly ex-
ported with the same export options as
the parent, except for fsid=. This
makes it impossible to not export a
child of a crossmnt filesystem. If some
but not all subordinate filesystems of a
parent are to be exported, then they
must be explicitly exported and the par-
ent should not have crossmnt set.
The nocrossmnt option can explictly dis-
able crossmnt if it was previously set.
This is rarely useful.
* c186282 <[email protected]>
| Here's what my boxes look like now :
| server
| /etc/exports :
| /home/nas/shar 192.168.0.0/24(rw,sync,no_root_squash,no_subtree_check)
|
Haven't followed this thread from the beginning, so maybe you've been
there before:
https://www.baeldung.com/linux/nfs-shares-export-import
basically says:
- you need to export both, the mount point /home/nas/shar
*AND* the mounted USB-filesystems /home/nas/shar/qshar[12]
- use crossmnt on /home/nas/shar in /etc/exports to un-hide the
USB-filesystems
On 03/04/2025 17:36, Ralf Fassel wrote:
* c186282 <[email protected]>
| Here's what my boxes look like now :
| server
| /etc/exports :
| /home/nas/shar 192.168.0.0/24(rw,sync,no_root_squash,no_subtree_check)
|
Haven't followed this thread from the beginning, so maybe you've been
there before:
https://www.baeldung.com/linux/nfs-shares-export-import
basically says:
- you need to export both, the mount point /home/nas/shar
*AND* the mounted USB-filesystems /home/nas/shar/qshar[12]
- use crossmnt on /home/nas/shar in /etc/exports to un-hide the
USB-filesystems
HTH
R'
I think those are alternatives. Both are not needed
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 33:52:51 |
| Calls: | 12,109 |
| Files: | 15,006 |
| Messages: | 6,518,330 |