From owner-freebsd-hackers Fri Feb 27 09:18:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22066 for freebsd-hackers-outgoing; Fri, 27 Feb 1998 09:18:00 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22059 for ; Fri, 27 Feb 1998 09:17:54 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.8.8/8.8.8) with ESMTP id SAA26926 for ; Fri, 27 Feb 1998 18:17:30 +0100 (MET) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.8/8.8.5) with ESMTP id SAA08581 for ; Fri, 27 Feb 1998 18:17:29 +0100 (CET) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id SAA05233 for ; Fri, 27 Feb 1998 18:17:30 +0100 (CET) From: Andre Albsmeier Message-Id: <199802271717.SAA00672@intern> Subject: 2.2.5-STABLE: is this a bug in umount? To: freebsd-questions@FreeBSD.ORG, hackers@FreeBSD.ORG Date: Fri, 27 Feb 1998 18:17:27 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, let's assume the following (done as root): mount /dev/sd3c /mnt tar cf /mnt/bla.tar some_big_directory While the tar is running we do the following in another shell: umount /mnt If we see a "Device busy" error we just repeat the umount again and again. Suddenly the system freezes for about 10 seconds and reboots. During the bootstrap the following message appears: bali daemon.alert savecore: reboot after panic: vinvalbuf: dirty bufs Now my question is: Is this the expected behaviour from umount? If you ask me why I do such a silly thing, it's because I mount my portable disk drive with amd. Then I start a timeconsuming job on this drive (in my case a tar from the network). After the default timeout of 5 minutes the amd unmounts the fs and the system crashes. I can reproduce this if you tell me. All that happens on a FreeBSD 2.2.5-STABLE system. Is this a bug (so I will send in a PR) or a feature? Thanks, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message