From owner-freebsd-questions@FreeBSD.ORG Sun Jul 28 14:12:48 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 579FFBF1 for ; Sun, 28 Jul 2013 14:12:48 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0604B2E02 for ; Sun, 28 Jul 2013 14:12:47 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r6SECdDC008875; Sun, 28 Jul 2013 08:12:39 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r6SECd0a008872; Sun, 28 Jul 2013 08:12:39 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 28 Jul 2013 08:12:39 -0600 (MDT) From: Warren Block To: Frank Leonhardt Subject: Re: Delete a directory, crash the system In-Reply-To: <51F4ECFD.5090502@fjl.co.uk> Message-ID: References: <51F3F290.9020004@cordula.ws> <51F420ED.1050402@fjl.co.uk> <20130728075447.4d6e0468.freebsd@edvax.de> <51F4ECFD.5090502@fjl.co.uk> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 28 Jul 2013 08:12:39 -0600 (MDT) Cc: Polytropon , freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jul 2013 14:12:48 -0000 On Sun, 28 Jul 2013, Frank Leonhardt wrote: > So it boils down to: > > a) Leave is is, as it can detect when the kernel has trashed its vnode table; > or > > b) It's probably caused by "expected" FS corruption, so handle it gracefully. It would be good to log a system error message like "filesystem may be corrupt" to give the user some clue other than a seemingly impossible error with no explanation.