From owner-freebsd-stable@FreeBSD.ORG Thu Jul 19 03:02:59 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1D76116A401 for ; Thu, 19 Jul 2007 03:02:59 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: from sigma.octantis.com.au (ns2.octantis.com.au [207.44.189.124]) by mx1.freebsd.org (Postfix) with ESMTP id D32B713C441 for ; Thu, 19 Jul 2007 03:02:58 +0000 (UTC) (envelope-from freebsd@meijome.net) Received: (qmail 21651 invoked from network); 18 Jul 2007 22:02:58 -0500 Received: from 203-206-233-219.dyn.iinet.net.au (HELO localhost) (203.206.233.219) by sigma.octantis.com.au with (DHE-RSA-AES256-SHA encrypted) SMTP; 18 Jul 2007 22:02:58 -0500 Date: Thu, 19 Jul 2007 13:02:52 +1000 From: Norberto Meijome To: freebsd-stable@FreeBSD.ORG, LoN_Kamikaze@gmx.de, idiotbg@gmail.com, josh@tcbug.org Message-ID: <20070719130252.6880b967@localhost> In-Reply-To: <200707181541.l6IFf4ht051775@lurza.secnetix.de> References: <200707181703.07480.idiotbg@gmail.com> <200707181541.l6IFf4ht051775@lurza.secnetix.de> X-Mailer: Claws Mail 2.10.0 (GTK+ 2.10.14; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: josh@tcbug.org, freebsd-stable@FreeBSD.ORG, olli@lurza.secnetix.de, idiotbg@gmail.com, LoN_Kamikaze@gmx.de Subject: Re: removing external usb hdd without unmounting causes reboot? 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: Thu, 19 Jul 2007 03:02:59 -0000 On Wed, 18 Jul 2007 17:41:04 +0200 (CEST) Oliver Fromme wrote: > If you have problems remembering, This is very interesting thread indeed.... I have found that mounting remote SMB shares will panic the kernel too, but only if i try to access it while 'gone' . If I remember correctly, if i thread carefully around it, i can manage to shutdown everything and it will only panic at the very last minute when the kernel tries to unmount. And, from my point of view, the explanation 'well, don't remove your mounted devices without unmounting them first' is rubbish - the problem is not necessarily users removing them, but ALL the reasons that could cause an unwanted and unplanned removal. Like a network outage in the case of smbfs. or someone killing the power on a USB device. I can't see why the whole kernel should die on you. Yes, i understand there are architectural reasons for this - then the architecture is not right anymore, i think. > another work-around > is to use the auto mounter daemon (amd(8)). It umounts > file systems automatically that are not in use. > Another nice feature of amd(8) is that you don't have > to mount the file system either -- Simply plug the USB > stick in, then access it, and amd(8) will automatically > mount it for you. Now, something I dont understand - amd runs at user level, and it mounts filesystems, and nothing dies when the filesystems go away (other than the obvious cases for the applications trying to write to the FS in question). Doesn't amd , at some point , have to tell the kernel 'please mount this filesystem' here or there? Isn't the kernel STILL involved in all this? and why doesnt the kernel panic when the FS goes away? The same goes for hald - it doesn't work flawlessly, but it does the trick, and i cant recall an instance when it crashed the kernel. re. USB disks, could we not by default use amd to mount USB devices? It seems the obvious native replacement for hald + polkitd + dbus I use in XFCE with Thunar on my laptop... TIA! _________________________ {Beto|Norberto|Numard} Meijome Never attribute to malice what can adequately be explained by incompetence. I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned.