From owner-freebsd-security Thu Nov 18 21:31:41 1999 Delivered-To: freebsd-security@freebsd.org Received: from phoenix.aye.net (phoenix.aye.net [198.7.192.5]) by hub.freebsd.org (Postfix) with SMTP id F2CB215515 for ; Thu, 18 Nov 1999 21:31:37 -0800 (PST) (envelope-from barrett@phoenix.aye.net) Received: (qmail 17302 invoked by uid 1000); 19 Nov 1999 05:31:55 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 19 Nov 1999 05:31:55 -0000 Date: Fri, 19 Nov 1999 00:31:55 -0500 (EST) From: Barrett Richardson To: David G Andersen Cc: Matthew Dillon , wes@softweyr.com, kris@hub.freebsd.org, trouble@netquick.net, freebsd-security@FreeBSD.ORG Subject: Re: secure filesystem wiping In-Reply-To: <199911190513.WAA26469@faith.cs.utah.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 18 Nov 1999, David G Andersen wrote: > So, one side point to Wes: > > Under 3.3-STABLE (Early October), obliterate on a 141 MB file on my > machine with 148M ram managed to deadlock my system. I recall something > about a problem like this with /dev/random, so I'm sure it's cleaned up in > -current. > I just experienced something similar with 3.1. Obliterate and top don't get along it seems. Seemed to wedge, but I sat tight for a while and it came back around after a bit. I have 2 CPUs, top had one nailed to the wall, and obliterate had the other. Finally getting obliterate killed brought my system back around but top was still chunking away, screen output was froze. CPU for obliterate was froze at 50 seconds in the top screen, but it actually had several minutes. It's repeatable. - Barrett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message