From owner-freebsd-current Tue Jul 20 10:57:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 23519153A2 for ; Tue, 20 Jul 1999 10:57:35 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id TAA21541; Tue, 20 Jul 1999 19:55:44 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Steven G. Kargl" Cc: freebsd-current@FreeBSD.ORG Subject: Re: is dumpon/savecore broken? In-reply-to: Your message of "Tue, 20 Jul 1999 10:42:56 PDT." <199907201742.KAA04068@troutmask.apl.washington.edu> Date: Tue, 20 Jul 1999 19:55:44 +0200 Message-ID: <21539.932493344@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199907201742.KAA04068@troutmask.apl.washington.edu>, "Steven G. Kar gl" writes: > >During the boot process I see > dumpon: crash dumps to /dev/da0s1b (4, 131073) > checking for core dump...savecore: can't find device 13/131073 >It seems that the the major device number is reset from 4 to 13. >troutmask:kargl[225] swapinfo >Device 1K-blocks Used Avail Capacity Type >/dev/#B13:0x20001 511872 0 511872 0% Interleaved Yes, all dev_t's which make it out of the kernel have cmajor numbers now. Try this change to savecore: /ddname = find_dev/s/BLK/CHR/ -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message