From owner-freebsd-current Tue May 29 1: 4:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from bsdone.bsdwins.com (www.bsdwins.com [192.58.184.33]) by hub.freebsd.org (Postfix) with ESMTP id 818F937B422 for ; Tue, 29 May 2001 01:04:55 -0700 (PDT) (envelope-from jwd@bsdwins.com) Received: (from jwd@localhost) by bsdone.bsdwins.com (8.11.3/8.11.0) id f4T80wg67655; Tue, 29 May 2001 04:00:58 -0400 (EDT) (envelope-from jwd) Date: Tue, 29 May 2001 04:00:58 -0400 From: John To: Ian Dowse Cc: John Polstra , current@FreeBSD.ORG, Matthew Jacob Subject: Re: wierdness with mountd Message-ID: <20010529040058.A67491@bsdwins.com> References: <200105281755.f4SHtNa20515@vashon.polstra.com> <200105290138.aa46895@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200105290138.aa46895@salmon.maths.tcd.ie>; from iedowse@maths.tcd.ie on Tue, May 29, 2001 at 01:38:08AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Ian Dowse's Original Message ----- > In message <200105281755.f4SHtNa20515@vashon.polstra.com>, John Polstra writes: > >In article , > >Matthew Jacob 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message