From owner-freebsd-bugs  Sun Nov  8 06:35:58 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA16209
          for freebsd-bugs-outgoing; Sun, 8 Nov 1998 06:35:58 -0800 (PST)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16201
          for <freebsd-bugs@FreeBSD.ORG>; Sun, 8 Nov 1998 06:35:55 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id BAA05196;
	Mon, 9 Nov 1998 01:35:26 +1100
Date: Mon, 9 Nov 1998 01:35:26 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811081435.BAA05196@godzilla.zeta.org.au>
To: cch@market.net.tw, freebsd-bugs@FreeBSD.ORG
Subject: Re: When dd writes write-protected floppy (in 3.0R)
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>    When I use dd to write a write-proteced floppy in FreeBSD 3.0 RELEASE,
>
>    I can not stop the process by press Ctrl-C, Ctrl-Z, or "kill -9 dd-pid".
>
>    Is this a bug?
>
>    details:
>
>        command: 
>
>            dd if=picobsd.bin of=/dev/fd0  # but I forget to enable
>                                           # the floppy writable

This is mostly a user error.  Writing to the buffered device prevents dd
from even seeing any write errors.  All the data is written successfully
to the buffer cache.  When the process exits (perhaps due to being killed)
it waits in exit() for the buffered data to be written (and further kills
have no effect).  The system doesn't give up after the first error when
it attempts to write the data.  It has no way of knowing whether the data
is important or if the next write will fail (you might have made the floppy
writable).

>        error messages:
>
>Nov  4 16:39:11 pico /kernel: fd0c: hard error writing fsbn 0 of 0-3 (ST0 40<abnrml> ST1 2<write_protect> ST2 0 cyl 0 hd 0 sec 1)
>Nov  4 16:39:11 pico /kernel: fd0c: hard error writing fsbn 4 of 4-7 (ST0 40<abnrml> ST1 2<write_protect> ST2 0 cyl 0 hd 0 sec 5)

Spewing console messages is a bug.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message