From owner-freebsd-bugs Sat Aug 30 04:10:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA12361 for bugs-outgoing; Sat, 30 Aug 1997 04:10:05 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA12355; Sat, 30 Aug 1997 04:10:01 -0700 (PDT) Date: Sat, 30 Aug 1997 04:10:01 -0700 (PDT) Message-Id: <199708301110.EAA12355@hub.freebsd.org> To: freebsd-bugs Cc: From: Zach Heilig Subject: Re: kern/4413: No way to unmount a floppy that goes bad while mounted. Reply-To: Zach Heilig Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/4413; it has been noted by GNATS. From: Zach Heilig To: Bruce Evans Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/4413: No way to unmount a floppy that goes bad while mounted. Date: Sat, 30 Aug 1997 06:01:05 -0500 On Sat, Aug 30, 1997 at 11:05:12AM +1000, Bruce Evans wrote: > This is a new bug in -current. In 2.2, errors for the superblock update > in ffs_unmount() are ignored. The fussier checking came from Lite2. > Other I/O errors in ffs_umount() are ignored in all versions. I/O errors > for the superblock update in ffs_mount() are ignored even in -current. > Bruce Are you sure this only affects -current? This is what uname on my system puts out (broken up to fit 80 columns): FreeBSD murkwood.gaffaneys.com 2.2-STABLE FreeBSD 2.2-STABLE #0: Mon Aug 25 03:01:54 CDT 1997 zach@murkwood.gaffaneys.com:/usr/src/sys/compile/ZACH i386 This is the system that couldn't unmount the floppy. -- Zach Heilig (zach@gaffaneys.com) -- Actually it's all quite simple. A technician at JPL messed up, and mixed a couple of frames between different films. The 'missing' engine flames from the apollo 11 LM ended up as the 'muzzle flashes' on the grassy knoll in the Zapruder film... Chris Stratton