From owner-freebsd-current@FreeBSD.ORG Thu Feb 19 12:40:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF34516A4CE for ; Thu, 19 Feb 2004 12:40:37 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87F6943D1F for ; Thu, 19 Feb 2004 12:40:37 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) i1JKeCTA033841; Thu, 19 Feb 2004 12:40:13 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)i1JKeC5K033840; Thu, 19 Feb 2004 12:40:12 -0800 (PST) (envelope-from sgk) Date: Thu, 19 Feb 2004 12:40:12 -0800 From: Steve Kargl To: Aaron Peterson Message-ID: <20040219204012.GA33771@troutmask.apl.washington.edu> References: <9615.162.114.211.143.1077213472.squirrel@mail.alpete.com> <20040219201520.GB44313@cicely12.cicely.de> <29352.162.114.211.143.1077222503.squirrel@mail.alpete.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <29352.162.114.211.143.1077222503.squirrel@mail.alpete.com> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org cc: ticso@cicely.de Subject: Re: bcwipe won't wipe a block device... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2004 20:40:37 -0000 On Thu, Feb 19, 2004 at 03:28:23PM -0500, Aaron Peterson wrote: > > I understand how devfs works, and i don't think that is the problem, > although perhaps I'm misunderstanding what you mean. > > dd if=/dev/urandom of=/dev/da0 > dd if=/dev/urandom of=/dev/fd0 > > these devices and nodes all exist, and these dd commands do as expected > and take off writing random data to the raw device. However i get the > errors mentioned previously when i try to use bcwipe on the same drives. > I would like to find a way to make bcwipe work. any suggestions about > what is causing this problem? Use ktrace or truss to see if bcwipe is actually opening /dev/da0 or /dev/rda0 or /dev/da0c. -- Steve