From owner-freebsd-questions@FreeBSD.ORG Tue Feb 17 22:30:56 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D571F1065726 for ; Tue, 17 Feb 2009 22:30:56 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from mail.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id A26ED8FC1A for ; Tue, 17 Feb 2009 22:30:56 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (mail.lan.rachie.is-a-geek.net [192.168.2.101]) by mail.rachie.is-a-geek.net (Postfix) with ESMTP id E2B2AAFC1FE; Tue, 17 Feb 2009 13:30:55 -0900 (AKST) From: Mel To: freebsd-questions@freebsd.org, Polytropon Date: Tue, 17 Feb 2009 13:30:55 -0900 User-Agent: KMail/1.9.10 References: <20090212062505.ca66b93e.freebsd@edvax.de> <200902161044.02542.fbsd.questions@rachie.is-a-geek.net> <20090217123757.4685b67b.freebsd@edvax.de> In-Reply-To: <20090217123757.4685b67b.freebsd@edvax.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902171330.55677.fbsd.questions@rachie.is-a-geek.net> Cc: Tim Judd Subject: Re: Determining process preventing umount of busy partition X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2009 22:30:58 -0000 On Tuesday 17 February 2009 02:37:57 Polytropon wrote: > On Mon, 16 Feb 2009 10:44:02 -0900, Mel wrote: > > Is this a one-time event or 100% reproducable? > > I've tried it several times, it can always be reproduced. > > > A likely scenario is: > > - You have squid running > > - You have rc_shutdowntimeout at default (30 seconds) > > I'm not sure if this setting (?) will have an effect after trying > the umount operation in SUM. Even if umount is retried after a > several time, /usr is still "busy". To explain the setting: If the shutdowntimeout is hit, rc stops killing daemons like it's supposed to do (effectively, stops calling rc.d scripts with SHUTDOWN keyword). This is weird, though. New theories (where are Chase, Cameron and Foreman when you need them!): fstat is lying, instead use: fstat -f /usr -m -v You have a mount on top of /usr, ie.: /usr/local or /usr/ports. -- Mel Problem with today's modular software: they start with the modules and never get to the software part.