From owner-freebsd-stable@FreeBSD.ORG Wed Jun 8 20:48:29 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D669E16A42D for ; Wed, 8 Jun 2005 20:48:29 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from luzifer.incubus.de (incubus.de [80.237.207.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FFC243D49 for ; Wed, 8 Jun 2005 20:48:29 +0000 (GMT) (envelope-from mkb@incubus.de) Received: from [192.168.2.10] (p54AABF8A.dip.t-dialin.net [84.170.191.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luzifer.incubus.de (Postfix) with ESMTP id DB6D430FE1; Wed, 8 Jun 2005 22:51:20 +0200 (CEST) Message-ID: <42A75A32.8050103@incubus.de> Date: Wed, 08 Jun 2005 22:50:58 +0200 From: Matthias Buelow User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050526) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Charles Swiger References: <20050608001306.3FB1F43D5C@mx1.FreeBSD.org> <42A6C7CE.9000002@incubus.de> <200506080908.02478.fcash@ocis.net> <42A71AE1.8020300@incubus.de> <6.2.1.2.0.20050608134054.06b8ccb0@64.7.153.2> <42A73293.5000105@incubus.de> In-Reply-To: X-Enigmail-Version: 0.91.0.0 OpenPGP: id=6FF22C9F; url=http://www.mkbuelow.net/mkbkeys Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Users Subject: Re: FreeBSD 5.4: Is it generally unstable? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jun 2005 20:48:30 -0000 Charles Swiger wrote: > Yanking a mounted device out from under Unix has always been a no- no. > It would be nice if FreeBSD handled this better, but this problem falls > into the "operator error: don't do that" category. I'm aware that some things have different priority but it is imho inacceptable over the long run, that if you (accidentally) rip out a mounted usb stick, that the system is unable to flush _any_ buffers and panics upon shutdown. This should be fixed, why doesn't the kernel just discard the buffers for the disappeared device? While it is an "operator error", users accidentally pulling usb sticks, iPods, etc. is something that just happens (happened to me 3 times already). > 5.3 and earlier especially have struck me as being noticably slower > than 4.10 or so, but there have been significant improvements since > then, and 5.4 and 4.1x seem to be comparable. To do better than a There has been a thread going on here some time ago where I wrote about this. mkb.