From owner-freebsd-current Tue Mar 28 4:52:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 2B0F337BE53 for ; Tue, 28 Mar 2000 04:52:16 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 8425 invoked from network); 28 Mar 2000 12:52:11 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 28 Mar 2000 12:52:11 -0000 Date: Tue, 28 Mar 2000 22:51:54 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Gary Jennejohn Cc: Jeroen Ruigrok van der Werven , Sheldon Hearn , Soren Schmidt , Brian Fundakowski Feldman , current@FreeBSD.ORG Subject: Re: DDB and dumping disk In-Reply-To: <200003281150.NAA49210@peedub.muc.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 28 Mar 2000, Gary Jennejohn wrote: > Jeroen Ruigrok van der Werven writes: > >I am currently only trying to figure out why the DDB way doesn't trigger > >savecore to recognise the dump. > > > > Maybe because kern.dumpdev has a different value and savecore can't > find a dump on it ? Have you tried setting kern.dumpdev by hand and > then manually invoking savecore ? Also, dumplo must have a consistent value. dumpdev should be set using ddb before the SYSINIT for the dump device is called, or better, never set dumpdev with ddb, but call setdumpdev(desired_dumpdev) directly at a suitable time. When setdumpdev() is not called, some sanity checks are bypassed, and dumplo is only statically initialized (to 0). This means that dumps go to the start of the dumpdev device instead of to the end. I think savecore will find the dump provided dumplo is consistently initialized, so the only problem with starting dumps at the start of the device is that this will clobber the label if the device contains the label. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message