From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 09:47:33 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 023521065670 for ; Thu, 15 Oct 2009 09:47:33 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 7FD758FC0A for ; Thu, 15 Oct 2009 09:47:32 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1MyMvf-00039v-0P for freebsd-current@freebsd.org; Thu, 15 Oct 2009 11:47:27 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 15 Oct 2009 11:47:26 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 15 Oct 2009 11:47:26 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Thu, 15 Oct 2009 11:47:10 +0200 Lines: 41 Message-ID: References: <20091014151026.699a5765@ernst.jennejohn.org> <20091014175600.GA55864@wep4035.physik.uni-wuerzburg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.23 (X11/20090928) In-Reply-To: <20091014175600.GA55864@wep4035.physik.uni-wuerzburg.de> Sender: news Subject: Re: buffers not syncing correctly during shutdown X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2009 09:47:33 -0000 Alexey Shuvaev wrote: > On Wed, Oct 14, 2009 at 03:13:00PM +0200, Ivan Voras wrote: >> Gary Jennejohn wrote: >> >>> I personally don't see why it ever should be handled. This is UNIX not >>> Windows and users should be smart enough to know that they umount such >>> devices before removing them otherwise nasty things can happen. >> Yes, but this is 2009 not 1978. >> > Well, the other side of being in 2009 is that filesystems have evolved too. > For example, I have UFS2 + SU on most of my removable media (sticks and > external hard drives). I was always interested how > this new "feature" of FreeBSD, to allow removable media disappear almost > silently, plays in this case? I see what you mean - UFS+SU is definitely not suitable for this environment. UFS without SU (mounted "normal" or "sync") OTOH is better. Windows mounts removable devices sync (unless told otherwise) since sometime around Win98SE. > I've had one case when I lost my external hard drive during > tar -xvf ports.tar.bz2 into it. I haven't touched it at the moment > (voltage spikes?). It was quite funny trying to browse through > the half-cached content then... have spent ~5 minutes before noticing > kernel message. > Re-plugging the drive has brought it back, with dirty filesystem, of course. > Maybe it would be better if the system paniced then :/) This would not help since the newly inserted device would get its own descriptor structure, whose pointer is obviously different from the old one... > Anyway, my point is that removing the media with most of > modern filesystems on it without unmounting is an operator error. > IMHO, the system should warn such an operators in one or the other way... Warn about what? That the media has been removed? AFAIK USB does this right now. Or you are suggesting another message from the file system layer saying: "see, about that in-transit data you are thinking about... well, it's gone now." :)