From owner-freebsd-questions Thu Jun 17 12:59:31 1999 Delivered-To: freebsd-questions@freebsd.org Received: from veenet.value.net (value.net [209.182.128.4]) by hub.freebsd.org (Postfix) with ESMTP id CCE5C152EE for ; Thu, 17 Jun 1999 12:59:28 -0700 (PDT) (envelope-from rfg@monkeys.com) Received: from monkeys.com (i180.value.net [206.14.136.180]) by veenet.value.net (8.8.7/8.7.4) with ESMTP id NAA12160 for ; Thu, 17 Jun 1999 13:03:03 -0700 (PDT) Received: from monkeys.com (LOCALHOST [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id NAA24124 for ; Thu, 17 Jun 1999 13:00:09 -0700 To: questions@freebsd.org Subject: What happens in this case? From: "Ronald F. Guilmette" Date: Thu, 17 Jun 1999 13:00:09 -0700 Message-ID: <24122.929649609@monkeys.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What will actually happen if I have a 140MB swap partition setup as my dump device, but I have 320MB of physical memory, and then a panic occurs? Will the kernel see that it only has 140MB of disk to work with and then just write that much and then give up? Or will it refuse to write anything? Or (worse) will it just keep on writing stuff even past the end of the partition in question (thus overwriting the data in OTHER partitions)? And anyway, why the heck does the dumpdev have to big as big as physical memory? I mean hay! What if I have 320MB physical, but only 100MB of that is actually allocated or in use at the moment of the panic? Then I should only need a 100MB swap partition to hold the panic dump, right? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message