From owner-freebsd-questions Thu Oct 14 12:19:56 1999 Delivered-To: freebsd-questions@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id E79DB14E08 for ; Thu, 14 Oct 1999 12:19:52 -0700 (PDT) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.9.3) id PAA00634 for freebsd-questions@FreeBSD.ORG; Thu, 14 Oct 1999 15:23:00 -0400 (EDT) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199910141923.PAA00634@cc942873-a.ewndsr1.nj.home.com> Subject: umountall requests To: freebsd-questions@FreeBSD.ORG (FreeBSD Questions) Date: Thu, 14 Oct 1999 15:23:00 -0400 (EDT) Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an old 486 that I slapped some old SCSI drives on and have been using as basically scratch space. About all I've been doing is CVSup of ports and src regularly at this one location on my site. I've also tried using it for /usr/obj space when a machine does not have local disk space for a make world. I NFS mount these on other machines to access them. The performance is not blazing, but I did not expect it to be, but I have had some more troublesome problems. On the client I get messages like, Oct 13 00:48:39 pc252 /kernel: nfs server backmail:/u1/obj-pc252: not responding Oct 13 00:48:39 pc252 /kernel: nfs server backmail:/u1/obj-pc252: is alive again Oct 13 12:03:17 pc252 /kernel: nfs server backmail:/u1/obj-pc252: not responding Oct 13 12:03:17 pc252 /kernel: nfs server backmail:/u1/obj-pc252: is alive again Oct 13 12:03:36 pc252 /kernel: nfs server backmail:/u1/obj-pc252: not responding Oct 13 12:03:37 pc252 /kernel: nfs server backmail:/u1/obj-pc252: is alive again Oct 13 12:45:35 pc252 /kernel: nfs server backmail:/u1/obj-pc252: not responding Oct 13 12:45:36 pc252 /kernel: nfs server backmail:/u1/obj-pc252: is alive again Oct 13 19:53:52 pc252 /kernel: nfs server backmail:/u1/obj-pc252: not responding Oct 13 19:53:53 pc252 /kernel: nfs server backmail:/u1/obj-pc252: is alive again Oct 13 23:45:48 pc252 /kernel: nfs server backmail:/u1/obj-pc252: not responding Oct 13 23:45:48 pc252 /kernel: nfs server backmail:/u1/obj-pc252: is alive again Over the course of a 24 hour period. There are no indications of network problems. On the server, I am getting a much more perplexing message, Oct 13 09:15:09 backmail mountd[6907]: umountall request from 123.45.67.89 from unprivileged port Oct 13 09:15:11 backmail last message repeated 3 times B Oct 13 10:13:06 backmail mountd[6907]: umountall request from 123.45.67.89 from unprivileged port Oct 13 10:13:06 backmail last message repeated 2 times Where 123.45.67.89 happens to be the IP address of the server (backmail) itself. Note that the times are not correlated between these two sets of messages on the different machines. I really do not have any idea what this second set of messages means. So, I ask the maillist, what could be causing the momentary lapses in NFS service seen by the client? Limitations of the server hardware? Network problems? And second, what do those messages on the server mean? Why is it sending umountall requests to itself from an unprivileged port? -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message