From owner-freebsd-hackers Mon Jun 28 19:26:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.ham.muohio.edu (dragon.ham.muohio.edu [134.53.147.33]) by hub.freebsd.org (Postfix) with ESMTP id 8F33514C23 for ; Mon, 28 Jun 1999 19:26:40 -0700 (PDT) (envelope-from howardjp@wam.umd.edu) Received: from localhost (howardjp@localhost) by dragon.ham.muohio.edu (8.9.3/8.9.3) with ESMTP id VAA31113; Mon, 28 Jun 1999 21:30:05 -0400 X-Authentication-Warning: dragon.ham.muohio.edu: howardjp owned process doing -bs Date: Mon, 28 Jun 1999 21:30:05 -0400 (EDT) From: Jamie Howard X-Sender: howardjp@dragon.ham.muohio.edu To: Zhihui Zhang Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: A way to crash system (3.1 & 3.2) with floppy In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Jun 1999, Zhihui Zhang wrote: > Suppose you have a *write-protected* DOS floppy and you do: > > # mount -t msdos /dev/fd0 /floppy <-- this is OK > > # cp somefile /floppy <-- a lot of error messages > > # umount /floppy <-- crash > > Now the system tries to sync the dirty buffers and fails. You have to > press a key to reboot. > > Is there anything wrong here or FreeBSD simply does not handle this in a > more elegant way? > > Thanks for any help. I had this happen to me the other day on my 3.2 system. I thought it was just me because I had mounted the disk several days before and figured I had swapped it out. I also had to reformat the floppy on a Win95 system to make it usable again. Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message