From owner-freebsd-questions Tue Apr 24 8: 5:35 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.communityconnect.com (mail.communityconnect.com [209.10.169.57]) by hub.freebsd.org (Postfix) with ESMTP id B2F2137B422 for ; Tue, 24 Apr 2001 08:05:32 -0700 (PDT) (envelope-from marius@mail.communityconnect.com) Received: from amavis by mail.communityconnect.com with scanned-ok (Exim 3.20 #1) id 14s4Ne-00072V-00 for questions@freebsd.org; Tue, 24 Apr 2001 11:05:30 -0400 Received: from [206.28.215.90] (helo=dt-9-45.hq.communityconnect.com) by mail.communityconnect.com with esmtp (Exim 3.20 #1) id 14s4Nd-000711-00; Tue, 24 Apr 2001 11:05:29 -0400 Date: Tue, 24 Apr 2001 11:05:31 -0400 (EDT) From: Marius X-Sender: marius@utterlux.hq.communitconnect.com To: questions@FreeBSD.org Cc: marius@mail.communityconnect.com Subject: nfs stuck in objtrm Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My company has a number of FreeBSD servers, 3.5-STABLE, that run thttpd to serve static content. The staic content is stored on nfs mounts. In general our FreeBSD servers are very fast, very efficient, they are the real workhorses of our server farm. We have two main problems that keep re-ocurring. One is that machines occationaly get stuck in vmopar. (Kernel Bug 14033) A problems which I believe is still unresolved. The second, more frequent annoyance is thttpd getting stuck in the 'objtrm' state while the nfs client hangs is vm_object_terminate(). Searching the archives I see this was once Kern/1159 but obviously that was a while ago. All my searches so far seem to indicate that is problem should have been cleared up long ago, yet I have had to reboot 3 servers in the last 12 hours because of it. The only thing we can do when this happens is ungracefully reboot the system without syncing the file system, as a normal reboot will just hang the machine as the objtrm process just won't die. I wish I knew a better way or could help to create a better resolution. Has anyone else seen this behavior recently? I will hopefully soon upgrade at least a test server to to the latest 4.x stable as well as the most recent release of thttpd so I can take full advantage of accept filters. Hopefully that will solve/help some of our woes. But I was wondering if anyone had any insite/experiece similar to ours with objtrm. -Marius M. Rex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message