Date: Tue, 20 Jul 1999 19:55:44 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: "Steven G. Kargl" <kargl@troutmask.apl.washington.edu> Cc: freebsd-current@FreeBSD.ORG Subject: Re: is dumpon/savecore broken? Message-ID: <21539.932493344@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 20 Jul 1999 10:42:56 PDT." <199907201742.KAA04068@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?21539.932493344>