From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 13:06:08 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 198811065670; Sun, 29 Jun 2008 13:06:08 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id C89BB8FC12; Sun, 29 Jun 2008 13:06:07 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mobileKamikaze.norad (unknown [92.116.216.54]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 747D88A0F85; Sun, 29 Jun 2008 14:42:45 +0200 (CEST) Message-ID: <48678334.9070500@bsdforen.de> Date: Sun, 29 Jun 2008 14:42:28 +0200 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.14 (X11/20080607) MIME-Version: 1.0 To: Kris Kennaway References: <48676D80.9010409@FreeBSD.org> <20080629111547.GC58634@edoofus.dev.vega.ru> <48677AD2.7030002@FreeBSD.org> In-Reply-To: <48677AD2.7030002@FreeBSD.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , Ruslan Ermilov Subject: Re: Attempt to write outside dump device boundaries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 13:06:08 -0000 Kris Kennaway wrote: > Ruslan Ermilov wrote: >> On Sun, Jun 29, 2008 at 01:09:52PM +0200, Kris Kennaway wrote: >>> I am frequently getting this when trying to minidump on amd64: >>> >>> Physical memory: 8168 MB >>> Dumping 2133 MB: 2118 2102 2086 2070 2054 2038 2022 2006 1990 1974 >>> 1958 1942 1926 1910 1894 1878 1862 1846 1830 1814 1798 1782 1766 1750 >>> 1734 1718 1702 1686 1670 1654 1638 1622 1606 1590 1574 1558 1542 1526 >>> 1510 1494 1478 1462 1446 1430 1414 1398 1382 1366 1350 1334 1318 1302 >>> 1286 1270 1254 1238 1222 1206 1190 1174 1158 1142 1126 1110 1094 1078 >>> 1062 1046 1030 1014 998 982 966 950 934 918 902 886 870 854 838 822 >>> 806 790 774 758 742 726 710 694 678 662 646 630 614 598 582 566 550 >>> 534 518 502 486 470 454 438 422 406 390 374 358 342 326 310 294 278 >>> 262 246 230 214 198 182 166 150 134 118 102 86 70 54 38 22 6Attempt >>> to write outside dump device boundaries. >>> >>> ** DUMP FAILED (ERROR 6) ** >>> = 0 >>> >> Yes, it happens most often on SMP machines. Previously it could >> overwrite data on your disk (in our case it destroyed GEOM mirrors). >> Now the attempt is logged and prevented. >> >> What's your question? ;) > > I'd have thought it was obvious: "why?" > > Kris Not enough swap space?