From owner-freebsd-current Mon Oct 12 08:24:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08738 for freebsd-current-outgoing; Mon, 12 Oct 1998 08:24:30 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08571 for ; Mon, 12 Oct 1998 08:23:06 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id LAA13243; Mon, 12 Oct 1998 11:23:57 -0400 (EDT) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Mon, 12 Oct 1998 11:23:57 -0400 (EDT) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Zach Heilig cc: current@FreeBSD.ORG Subject: Re: bitten 3 times already. In-Reply-To: <19981012023022.A18715@znh.org> 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 Mon, 12 Oct 1998, Zach Heilig wrote: > > this is the third time freebsd has decided that wd0s1b wasn't "comfy" > > enough for a crashdump and ate a different partition while dumping. > .... > > also, anyone have something i can do to get a dump of my partitions to > > examine why it's confusing the crashdump mechanism? > > A few questions that maybe might help to sort this out (You can mail these > answers to me if you want me to check them): > > Is that swap partition at least 64K bigger than the amount of RAM you have? > (It is good to make at least one swap partition ~25-50% bigger than physical > ram if you have multiple swap partitions.. and at least twice as big if > you have only one swap partition). > > Does /usr and the swap device overlap (check 'disklabel wd0s1', /usr is usually > on the next partition after the swap partition in the default install)? > (size + offset should be equal to the offset of the next used partition) > > check what 'dumpon -v /dev/wd0s1b' says. > make sure 'sysctl kern.dumpdev' matches. disklabel -r wd0s1 a: 81920 0 4.2BSD 0 0 0 # (Cyl. 0 - 5*) b: 614400 163840 swap # (Cyl. 10*-48*) c: 8385867 0 unused 0 0 # (Cyl. 0 -521*) e: 81920 81920 4.2BSD 0 0 0 # (Cyl. 5*-10*) f: 4096000 778240 4.2BSD 0 0 0 # (Cyl. 48*-303*) g: 3511627 4874240 4.2BSD 0 0 0 # (Cyl. 303*-521*) /dev/wd0s1a on / (local, soft-updates, writes: sync 4 async 375) /dev/wd0s1f on /usr (local, soft-updates, writes: sync 12 async 7952) /dev/wd0s1e on /var (local, soft-updates, writes: sync 77 async 350) /dev/wd0s1g on /usr/home (local, soft-updates, writes: sync 201 async1131) /dev/wd0s2e on /spare (local, soft-updates, writes: sync 2 async 0) Please for the love of god don't tell me all my partitions overlap by one cyl :( (well, unless they do, so i can dump them quick and fix this) :) top: Mem: 44M Active, 29M Inact, 16M Wired, 33M Cache, 7340K Buf, 616K Free Swap: 300M Total, 300M Free So i have plenty of swap vs RAM which is 128megs I double checked the dump device before _the bad thing_ happened. it said: kern.dumpdev: { major = 0, minor = 131073 } brw-r----- 1 root operator 0, 0x00020001 Oct 11 14:58 /dev/wd0s1b Also: wdc0 at 0x1f0-0x1f7 irq 14 flags 0x7fff7fff on isa wdc0: unit 0 (wd0): , LBA, DMA, multi-block-16, sleep-hack wd0: 8063MB (16514064 sectors), 17475 cyls, 15 heads, 63 S/T, 512 B/S i'm quite sure i have LBA translations going on, however i'm kinda certain that the disk driver isn't running amok because all my other partitions were fine (except /usr) thank you for taking the time to help me with this, go an idea of what's going on here? thanks, Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message