From owner-freebsd-current Mon Oct 5 02:39:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11106 for freebsd-current-outgoing; Mon, 5 Oct 1998 02:39:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA11085 for ; Mon, 5 Oct 1998 02:39:13 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id TAA17977; Mon, 5 Oct 1998 19:08:46 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id TAA28227; Mon, 5 Oct 1998 19:08:46 +0930 (CST) Message-ID: <19981005190846.L27781@freebie.lemis.com> Date: Mon, 5 Oct 1998 19:08:46 +0930 From: Greg Lehey To: Karl Pielorz Cc: current@FreeBSD.ORG Subject: Re: Panic with heavy diskaccess - current as of 10/04/98 References: <19981005183916.J27781@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Karl Pielorz on Mon, Oct 05, 1998 at 10:18:34AM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 5 October 1998 at 10:18:34 +0100, Karl Pielorz wrote: > > On Mon, 5 Oct 1998, Greg Lehey wrote: > >> On Monday, 5 October 1998 at 9:04:38 +0100, Karl Pielorz wrote: >>> >>> Hi All, >>> >>> I keep seeing the panic below while I'm trying to untar a 1.5Gb file on my >>> system... >>> >> Well, it's nice to have something consistent. > > Yes, it's very consistent - usually about 30 - 40 seconds after hitting > 'enter' on the 'tar zxvf my_home_dir.tgz' ;-) Hmm. That does rather sound like a size problem. >>> The panic details are below - I've heard nasty things about crashdumps at >>> the moment - are these safe to enable now? >> >> I haven't seen any problems. What have you seen? > > People were complaining they were overwriting volumes, and not writing to > the crash device specified... :-( Oh. I didn't see that. >> No, this doesn't look like a termination problem. It would be really >> nice to get a dump of it. Looks like it could be a size problem. I >> did some changes in this area a while back. Which version of vinum >> are you running? > > I'll see if I can get some crash dumps going (after I've backed up ;-) - > > The vinum is the one that's in the 3.0-Current source tree, I'm not too > sure how 'new' this version is... Are you maintaining the version in the > tree - or are the updates still on your system? I'm checking in the updates as soon as I'm sure they're kosher. > (Is there anywhere in /usr/src/lkm/vinum I can find the version number?) Not any more. It's 3.0. You can look at the $Id$ strings in the sources, but if you're using -CURRENT, this shouldn't be happening. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message