From owner-freebsd-questions@FreeBSD.ORG Mon Mar 6 21:52:27 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BA1616A423 for ; Mon, 6 Mar 2006 21:52:27 +0000 (GMT) (envelope-from chad@zetaweb.com) Received: from rs27.luxsci.com (rs27.luxsci.com [66.216.127.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7E1F43D73 for ; Mon, 6 Mar 2006 21:52:26 +0000 (GMT) (envelope-from chad@zetaweb.com) Received: from [192.168.1.101] (static-151-201-138-242.pitt.east.verizon.net [151.201.138.242]) (authenticated bits=0) by rs27.luxsci.com (8.13.5/8.13.5) with ESMTP id k26LqOSf017819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 6 Mar 2006 15:52:25 -0600 Message-ID: <440CAF18.4080605@zetaweb.com> Date: Mon, 06 Mar 2006 16:52:24 -0500 From: Chad Whitacre User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Kris Kennaway References: <20060306205736.GA50469@xor.obsecurity.org> <440CA2FD.3070804@zetaweb.com> <20060306211051.GA50768@xor.obsecurity.org> <440CAACE.7000504@zetaweb.com> <20060306214419.GA51866@xor.obsecurity.org> In-Reply-To: <20060306214419.GA51866@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: possible umount bugs (was Re: "Panic: unmount: dangling vnode") 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: Mon, 06 Mar 2006 21:52:27 -0000 Kris, > The rule of thumb is that user code should not cause kernel panics. Good to know, thanks. > But all software has bugs, of course. Understood. This is just the first bug I've personally hit in FreeBSD in 4 years of use. /me weeps for his lost innocence >> Is it likely that known umount problems explain the other symptom >> ("umount: unmount of /backup failed: Device busy")? > > That's completely standard and just means something still had a file > open on that filesystem. Use fstat or lsof to find out what. Another good tip, thanks. >> This is actually a production box, so I can't do too much testing on it. >> I may be able to install the patch, though, in which case I will report >> back. > > Thanks. Let me know if there's any other info besides a patch report that might be helpful. chad