From regnauld@S44.eu.org Fri Sep 24 18:04:04 1999
Return-Path: <regnauld@S44.eu.org>
Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2])
	by hub.freebsd.org (Postfix) with ESMTP id 4C75014D10
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 24 Sep 1999 18:04:01 -0700 (PDT)
	(envelope-from regnauld@S44.eu.org)
Received: from ns.int.ftf.net (fw2.ftf.dk [192.168.1.2] (may be forged))
	by mail.ftf.dk (8.9.3/8.9.3/gw-ftf-1.2) with ESMTP id DAA17780
	for <FreeBSD-gnats-submit@freebsd.org>; Sat, 25 Sep 1999 03:02:49 +0200 (CEST)
Received: (from uucp@localhost)
	by ns.int.ftf.net (8.9.2/8.9.3) with UUCP id DAA12557
	for FreeBSD-gnats-submit@freebsd.org; Sat, 25 Sep 1999 03:09:22 +0200 (CEST)
Received: (from regnauld@localhost)
	by flow.S44.eu.org (8.9.3/8.9.1/stimpy-1.0) id DAA11769;
	Sat, 25 Sep 1999 03:07:39 +0200 (CEST)
	(envelope-from regnauld)
Message-Id: <199909250107.DAA11769@flow.S44.eu.org>
Date: Sat, 25 Sep 1999 03:07:39 +0200 (CEST)
From: Phil Regnauld <regnauld@S44.eu.org>
Reply-To: regnauld@S44.eu.org
To: FreeBSD-gnats-submit@freebsd.org
Subject: Panic with dd on block/"cooked" devices using 3.3-RELEASE
X-Send-Pr-Version: 3.2

>Number:         13940
>Category:       kern
>Synopsis:       Panic with dd on block/"cooked" devices using 3.3-RELEASE
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Sep 24 18:10:01 PDT 1999
>Closed-Date:    Mon Jul 9 16:28:59 PDT 2001
>Last-Modified:  Mon Jul 09 16:31:11 PDT 2001
>Originator:     Phil Regnauld
>Release:        FreeBSD 3.3-RELEASE i386
>Organization:
Freenix User Group
>Environment:

	PII-400, 128 MB RAM, NCR875 UW SCSI, 1 x 4.5 GB SCSI IBM,
	2 x 10 GB EIDE QUANTUM, 3.3-RELEASE

>Description:

	When using dd to copy a block device to another (i.e.:
	/dev/wd0a -> /dev/wd2a for example), the system panics.

	Greg Lehey <grog@lemis.com> is aware of the problem.

>How-To-Repeat:

	# dd if=/dev/rwd0a of=/dev/rwd2a bs=1024k conv=notrunc
	dd: /dev/rwd2a: Read-only file system
	1+0 records in
	0+0 records out
	0 bytes transferred in 0.059349 secs (0 bytes/sec)
	# mount
	da0s1a on / (local, read-only, writes: sync 2 async 0)
	# dd if=/dev/wd0a of=/dev/wd2a bs=1024k conv=notrunc
	195+1 records in
	195+1 records pout
	a204800000 bytes ntransferred in 2i8.291105 secs (7c239024 bytes/sec:)
 	vinvalbuf: dirty bufs
	Debugger("panic")
	Stopped at      Debugger+0x37:  movl    $0,in_Debugger

>Fix:
	
	


>Release-Note:
>Audit-Trail:

From: Dag-Erling Smorgrav <des@ofug.org>
To: freebsd-gnats-submit@freebsd.org
Cc:  
Subject: Re: kern/13940
Date: 11 Jun 2001 15:17:49 +0200

 Does this problem still occur in newer FreeBSD versions (which no
 longer has block devices)?
 
 DES
 -- 
 Dag-Erling Smorgrav - des@ofug.org

From: Giorgos Keramidas <charon@labs.gr>
To: freebsd-gnats-submit@FreeBSD.org, regnauld@S44.eu.org
Cc:  
Subject: Re: kern/13940: Panic with dd on block/"cooked" devices using 
 3.3-RELEASE
Date: Wed, 13 Jun 2001 22:45:57 +0300

 Phil Regnauld wrote:
 
 > When using dd to copy a block device to another (i.e.:
 > /dev/wd0a -> /dev/wd2a for example), the system panics.
 >
 > Greg Lehey <grog@lemis.com> is aware of the problem.
 
 Does this occur only in 3.3-RELEASE ?
 
 Is it a problem of the wd driver only?
 I tested this on 4-STABLE with ad driver for atapi disks,
 and dd(1) works for me.  With floppies, it works too.
 I even tried copying a floppy to a raw disk device (
 
 Can you please provide with more information on this?
 I'm most interested to know
 
 a) if this bug appears only in 3.3-RELEASE or is present
    in newer 3.x releases too
 b) if this is a bug of the wd driver, or you seem to be
    having the same problems with ad driver too.
 
 Thank you.
 
 -giorgos
State-Changed-From-To: open->closed 
State-Changed-By: iedowse 
State-Changed-When: Mon Jul 9 16:28:59 PDT 2001 
State-Changed-Why:  

Although the underlying problem here still exists, we no longer have 
block devices, so it cannot be triggered in the way described by 
this PR. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=13940 
>Unformatted:
