----- Ian Dowse's Original Message -----
> In message <[EMAIL PROTECTED]>, John Polstra writes:
> >In article <[EMAIL PROTECTED]>,
> >Matthew Jacob <[EMAIL PROTECTED]> wrote:
> >> May 28 10:21:43 farrago mountd[217]: can't delete exports for /tmp
> >> May 28 10:21:43 farrago mountd[217]: can't delete exports for /usr/obj
> >
> >I've been seeing this too, on a -current system from around May 5.
>
> This sounds like there are stale entries in /var/db/mountdtab, but
> I'm not familiour enough with the purpose of mountdtab to know why
> this is happening. I'll look into this further over the next few
> days; for now maybe try cleaning out mountdtab manually?
>
> Ian
Hi,
Some info... I've looked into a bit previously.. I have no mountdtab file:
%find /var -name 'mount*'
/var/db/mounttab
/var/log/mount.today
/var/log/mount.yesterday
/var/run/mountd.lock
/var/run/mountd.pid
What I have mounted, though it is not a part of this issue..
%cat /var/db/mounttab
990745123 snapserv /pub
990745123 snapserv /mirror/ncvs
and then reboot the system:
/boot/kernel/kernel: May 29 03:37:57 FreeBSD mountd[270]: can't delete exports for /
/boot/kernel/kernel: May 29 03:37:57 FreeBSD mountd[270]: can't delete exports for /usr
/boot/kernel/kernel: May 29 03:37:57 FreeBSD mountd[270]: can't delete exports for /tmp
/boot/kernel/kernel: May 29 03:37:57 FreeBSD mountd[270]: can't delete exports for /var
/boot/kernel/kernel: May 29 03:37:57 FreeBSD mountd[270]: can't delete exports for
/usr/obj
/boot/kernel/kernel: May 29 03:37:57 FreeBSD mountd[270]: can't delete exports for
/snap
Looking in /usr/src/sbin/mountd/mountd.c, under line 930
shows the following:
num = getmntinfo(&fsp, MNT_NOWAIT);
and then runs through a loop 'num' times trying to
delete any export for each entry. Maybe it should check
to see if there is an export before attempting to delete it
by using the MNT_EXPORTED request? Note: These MNT_xxx definitions
appear to be only partially documented in mount(2).
If you kill and restart mountd the logic appears correct.
Bringing mountd up on a newly booted system appears to be the
oddball case.
Hope this helps..
-john
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
