From owner-freebsd-current@FreeBSD.ORG Fri Sep 30 20:27:00 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD0D216A41F; Fri, 30 Sep 2005 20:27:00 +0000 (GMT) (envelope-from listas@informatica.info) Received: from deneb.informatica.info (lincl214.informatica.info [86.109.161.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CA7943D48; Fri, 30 Sep 2005 20:26:59 +0000 (GMT) (envelope-from listas@informatica.info) Received: from [192.168.1.68] (231.Red-83-57-45.dynamicIP.rima-tde.net [83.57.45.231]) (authenticated bits=0) by deneb.informatica.info (8.13.1/8.13.1) with ESMTP id j8UKQn4g023281 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Sep 2005 22:26:51 +0200 Message-ID: <433D9F93.1040802@informatica.info> Date: Fri, 30 Sep 2005 22:26:59 +0200 From: Listas User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: es-es, en, ca MIME-Version: 1.0 To: Robert Watson References: <433D8B12.9020801@informatica.info> <20050930190403.GA93829@xor.obsecurity.org> <20050930210228.D71864@fledge.watson.org> In-Reply-To: <20050930210228.D71864@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, Kris Kennaway Subject: Re: Losing ssh session when doing intensive disk I/O & background fsck with RELENG_6 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: Fri, 30 Sep 2005 20:27:00 -0000 Only have this in the dump directory: vega# ll /var/crash total 2 -rw-r--r-- 1 root wheel 5 Sep 19 00:24 minfree vega# cat /var/crash/minfree 2048 No vmcore, but haven't seen any system crash anyway. I use the system defaults: dumpdev="AUTO" # Device to crashdump to (device name, AUTO, or dumpdir="/var/crash" # Directory where crash dumps are to be stored savecore_flags="" # Used if dumpdev is enabled above, and present. Carlos Robert Watson wrote: > > On Fri, 30 Sep 2005, Kris Kennaway wrote: > >>> The boot process is trying to configure the dump device before swapon >>> and it fails, but that's not the real problem I report here. >> >> >> It's not clear that it's a problem at all. dump devices don't have to >> be pre-existing swap devices. If you tell your kernel to dump on >> /dev/ar0s1b it should be fine. > > > At some point someone changed the default setting to "automatically > configure dumping" which resulted in odd warnings during the boot. I've > trimmed a few, and hope to trim the last few. Autoconfiguration of > dumps is neat and all, but lots of odd warnings for users isn't really. > It would be interesting to know if it works though -- the warnings > suggest that dumps aren't found because the dump device isn't > autoconfigured until after dumps are checked for... > > Robert N M Watson >