Re: NFSv4.2: One share not automounting

From: Larry Rosenman <ler_at_lerctr.org>
Date: Wed, 23 Nov 2022 21:37:55 UTC

yes. just a subdirectory of /:

❯ df /vault/backup
Filesystem                       Size    Used   Avail Capacity  Mounted 
on
zroot/ROOT/14-2022_11_23-0001    7.8T    3.4G    7.8T     0%    /

ler in 🌐 borg in ~ via C v14.0.5-clang on ☁️  (us-east-1)
❯

and I did mention what version:
This has been happening for a while.  FreeBSD 14-CURRENT as of Tue Nov
22 23:59:16 CST 2022

❯ uname -a
FreeBSD borg.lerctr.org [1] 14.0-CURRENT FreeBSD 14.0-CURRENT #29
ler/freebsd-main-changes-n259398-496d4d928269: Tue Nov 22 23:59:16 CST
2022
root@borg.lerctr.org:/usr/obj/usr/src/amd64.amd64/sys/LER-MINIMAL amd64

On 11/23/2022 3:33 pm, Rick Macklem wrote:

> On Wed, Nov 23, 2022 at 8:41 AM Larry Rosenman <ler@lerctr.org> wrote:
> 
>> /vault/backup is just a directory local on the client.
> 
> And /vault/backup/TBH is just a subdirectory of that file system?
> 
> I vaguely recall a PR that looked like this, where there were
> nullfs mounts and I twiddled things so that "late" could be used,
> but that might only be for FreeBSD 14/current. I can't recall if
> the changes were MFC'd. You did not mention what version of
> FreeBSD you were using.
> 
> rick
> 
> Late causes other issues with both mounts and the rest of the boot 
> sequence.
> 
> On 11/23/2022 8:59 am, Rick Macklem wrote:
> 
> On Tue, Nov 22, 2022 at 10:25 PM Larry Rosenman <ler@lerctr.org> wrote: 
> CAUTION: This email originated from outside of the University of 
> Guelph. Do not click links or open attachments unless you recognize the 
> sender and know the content is safe. If in doubt, forward suspicious 
> emails to IThelp@uoguelph.ca
> 
> I have the following 2 entries in /etc/fstab:
> #########
> freenas.lerctr.org:/mnt/data/TBH    /vault/backup/TBH    nfs
> rw,nfsv4,minorversion=2,nconnect=8 0 0
> freenas.lerctr.org:/mnt/data/BACULA /vault/backup/BACULA nfs
> rw,nfsv4,minorversion=2,nconnect=8 0 0
> 
> the top one (ending in /TBH) doesn't mount at boot, but if I do a 
> manual
> mount, it's fine.
> Is /vault/backup a mount point on the client?
> (You didn't show the rest of your /etc/fstab.)
> If so, it might be a timing thing w.r.t. when /vault/backup
> gets mounted.
> 
> You could try the "late" mount option, to see if that helps.
> 
> Other than that, I cannot think why the first one would not work.
> 
> rick
> ps: Normally NFSv4 mounts a tree of file systems on the server and,
> as such, a single mount to a server is used, but doing multiple
> mounts should work.
> How can I get data to diagnose this issue?
> 
> This has been happening for a while.  FreeBSD 14-CURRENT as of Tue Nov
> 22 23:59:16 CST 2022
> 
> ❯ uname -a
> FreeBSD borg.lerctr.org [1] 14.0-CURRENT FreeBSD 14.0-CURRENT #29
> ler/freebsd-main-changes-n259398-496d4d928269: Tue Nov 22 23:59:16 CST
> 2022
> root@borg.lerctr.org:/usr/obj/usr/src/amd64.amd64/sys/LER-MINIMAL amd64
> 
> --
> Larry Rosenman                     http://www.lerctr.org/~ler
> Phone: +1 214-642-9640                 E-Mail: ler@lerctr.org
> US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106

-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 214-642-9640                 E-Mail: ler@lerctr.org
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106

-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 214-642-9640                 E-Mail: ler@lerctr.org
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106


Links:
------
[1] http://borg.lerctr.org