Date: Thu, 19 Feb 2004 15:50:09 -0500 (EST) From: "Aaron Peterson" <aaron@alpete.com> To: "Steve Kargl" <sgk@troutmask.apl.washington.edu> Cc: Aaron Peterson <aaron@alpete.com> Subject: Re: bcwipe won't wipe a block device... Message-ID: <46490.162.114.211.143.1077223809.squirrel@mail.alpete.com> In-Reply-To: <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> <20040219204012.GA33771@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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 > The output was too long I though to post back to the list from ktrace/kdump... you can read it here: http://www.alpete.com/bcwipe.kdump.txt I'm not so good at understanding it since it is the first time I've ever used ktrace :) I think I understand some of it, but I still don't understand the problem, so perhaps you guys can shed some light on the subject for me...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46490.162.114.211.143.1077223809.squirrel>