lo0 has 127.0.0.1, ::1 (both first in their lists). It also has a pile of
other IPs that are used by jails. This has not changed
On Thu, Nov 21, 2024 at 6:35 PM Rick Macklem wrote:
> On Thu, Nov 21, 2024 at 1:22 PM Zaphod Beeblebrox
> wrote:
> >
> >
> > I
I've tried a lot of different combinations of rc variables. On 13.3 and
14.1, nfsd in most (non-v4-only) configurations registers to rpcbind as
expected. This is true of restarting nfsd and using nfsd -r.
However on 14.2, I can't contrive any configuration that registers to
rpcbind. Minimally,
t;-6 -L"
rpc_lockd_enable="YES"
rpc_statd_enable="YES"
on the server.
On Thu, Nov 21, 2024 at 3:52 PM Zaphod Beeblebrox wrote:
> This a previously working situation with the client being 14.1. The
> server was originally 13.3. Is now 14.2-B1.
>
> I have t
This a previously working situation with the client being 14.1. The server
was originally 13.3. Is now 14.2-B1.
I have tried the v4 enable, v4 only and no v4 setting. The client mounts
with
yak:/home/dgilbert /d/yak/home/dgilbert nfs rw,-3,-T,-l,-i,-b 0 0
yak:/home/dclarke /d/yak/ho
I upgraded a 13.3 machine to 14.2-BETA1 this week. Of the many things it
does, it is an NFS server for one thing. I'm a little bit pulling my hair
out at this point, but the most glaring thing wrong is:
[2:62:362]root@saiga:~> nfsd -r -u -t
[2:64:364]root@saiga:~> rpcinfo
program version neti
It can be more straightforward to update the gmirror, however. I've done
this with UFS --- old boot, pair of UFS/GMIRROR usb sticks that then boot
to a ZFS array that the BIOS couldn't see (so UFS only contained /boot and
/rescue). It's easier to know that the boot is updated identically if
gmirr
The point I want to reiterate, however, is this error is tossed out when my
setup fails and the answer is a full powerdown of the motherboard --- after
which the disks are adequately described.
On Wed, Apr 27, 2022 at 9:26 AM Warner Losh wrote:
>
>
> On Wed, Apr 27, 2022 at 7:05 AM Larry Rosenma
I have had this happen too... in my case an TR4 motherboard booting from 2x
4T (WD red) and an NMVE cache/log. What I've found is that the BIOS is
faulty for some reason on reboot --- and that a complete poweroff (where
the board power -- and the LEDs go out) is required ... and then everything
bo
