Re: bad exports list line message happening suddenly on 15-stable after buildworld/kernel upgrade
Rick Macklem <[email protected]> Thu, 21 May 2026 17:34:25 -0700
| Newsgroups | gmane.os.freebsd.devel.file-systems |
|---|---|
| Message-ID | <CAM5tNy7U+06MG1UzHRuVO5c-tKBYBrjbML11xAge724YaN7Vzw@mail.gmail.com> |
On Thu, May 21, 2026 at 4:41 PM void <[email protected]> wrote: > > Hi, > > I'm seeing these lines appear in /var/log/messages on the nfs server: > > === > May 21 17:17:30 desktop mountd[34297]: can't change attributes for /external20tb/04: netcred already exists for given addr/mask > May 21 17:17:30 desktop mountd[34297]: can't change attributes for /external20tb/00: netcred already exists for given addr/mask > May 21 17:17:30 desktop mountd[34297]: bad exports list line '/external20tb/00 -maproot' > May 21 17:17:30 desktop mountd[34297]: can't change attributes for /external20tb/02: netcred already exists for given addr/mask > May 21 17:17:30 desktop mountd[34297]: bad exports list line '/external20tb/02 -maproot' > May 21 17:17:30 desktop mountd[34297]: can't change attributes for /external20tb/04: netcred already exists for given addr/mask > May 21 17:17:30 desktop mountd[34297]: bad exports list line '/external20tb/04 -maproot' > === > > The exports actually work, in that they can be used by clients laptop1 and rpi4b > > They are zfs sharenfs dirs. > > /etc/exports looks like this : > > === > /external20tb/00 -maproot=root -alldirs laptop1 rpi4b > /external20tb/02 -maproot=root -alldirs laptop1 rpi4b > /external20tb/04 -maproot=root -alldirs laptop1 rpi4b And each of the above lines still refer to separate file systems? (If not, the message is telling you that it is already exported by a previous line and the mounts work because the file system was exported by the previous line.) Check to make sure /external20tb/00 etc are separate file systems. If they have never been separate file systems, that message should have always showed up. rick > === > > /etc/zfs/exports is identical > > What's going on? This only started happening after upgrading from: > FreeBSD 15.0-STABLE stable/15-n282003-d2fb6b8f80cc > > to: > FreeBSD 15.1-STABLE #0 stable/15-n283597-3ae682909950 > -- >