From owner-freebsd-current@FreeBSD.ORG Mon Jun 30 02:17:30 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 AF2471065670 for ; Mon, 30 Jun 2008 02:17:30 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 6122F8FC17 for ; Mon, 30 Jun 2008 02:17:29 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.local ([192.168.254.200]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m5U1gmPR069639; Sun, 29 Jun 2008 19:42:51 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <48683A18.6080509@samsco.org> Date: Sun, 29 Jun 2008 19:42:48 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.13) Gecko/20080313 SeaMonkey/1.1.9 MIME-Version: 1.0 To: Julian Elischer References: <48676D80.9010409@FreeBSD.org> <20080629111547.GC58634@edoofus.dev.vega.ru> <48677AD2.7030002@FreeBSD.org> <48678334.9070500@bsdforen.de> <4867E2EE.3070008@elischer.org> In-Reply-To: <4867E2EE.3070008@elischer.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=3.8 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: Dominic Fandrey , FreeBSD Current 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: Mon, 30 Jun 2008 02:17:30 -0000 Julian Elischer wrote: > Dominic Fandrey wrote: >> 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? > > It used to check that before starting.. did that check get removed? It does check when it starts. The problem is that the size grows after that. Scott