From owner-freebsd-current Mon May 27 15:20:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA21539 for current-outgoing; Mon, 27 May 1996 15:20:06 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA21457; Mon, 27 May 1996 15:19:48 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA09269; Mon, 27 May 1996 15:18:06 -0700 From: Terry Lambert Message-Id: <199605272218.PAA09269@phaeton.artisoft.com> Subject: Re: try this .. panic :-( To: bde@zeta.org.au (Bruce Evans) Date: Mon, 27 May 1996 15:18:06 -0700 (MST) Cc: current@FreeBSD.org, imb@scgt.oz.au, stable@FreeBSD.org In-Reply-To: <199605251942.FAA28584@godzilla.zeta.org.au> from "Bruce Evans" at May 26, 96 05:42:23 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > >i) insert write protected floppy > >ii) dd if=boot.flp of=/dev/fd0 bs=9k > >iii) oops .. WP errors .. pulls floppy out of drive w/o hitting ^C first > >iv) panic: page not present > > This has been reported before, but I couldn't duplicate it then or now > in -current. > > Don't use block disk devices if you value your data. I/O errors aren't > reported to the application. They are only logged. Perhaps they should > be reported by close(). dd would still ignore them. It doesn't even > bother to close the output file explicitly :-(. Was -current changed so that full page writes don't cause the system to do a read-before-write? This would be the correct fix for the problem. One *could* use the unsigned char bitmap to take this down to the 512b block level on a 4k or larger block size FFS, regardless of frag size. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.