From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 10 20:16:58 2013 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E1936CA7 for ; Wed, 10 Jul 2013 20:16:58 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from aussmtpmrkps320.us.dell.com (aussmtpmrkps320.us.dell.com [143.166.224.254]) by mx1.freebsd.org (Postfix) with ESMTP id B7AFB199A for ; Wed, 10 Jul 2013 20:16:58 +0000 (UTC) X-Loopcount0: from 64.238.244.148 X-IronPort-AV: E=Sophos;i="4.87,1038,1363150800"; d="scan'208";a="34508446" Message-ID: <51DDC133.7010401@vangyzen.net> Date: Wed, 10 Jul 2013 15:16:51 -0500 From: Eric van Gyzen User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130702 Thunderbird/17.0.7 MIME-Version: 1.0 To: Julian Elischer Subject: Re: possible changes from Panzura References: In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jul 2013 20:16:58 -0000 On 07/10/2013 13:16, Julian Elischer wrote: > I'm going through all the internal changes my current employer has made, categorizing them > into "proprietary" and "can feed back to FreeBSD". > > I will probably send out emails like this several times seeking feedback on whether a particular patch is considered useful or not.. > these are verse 8.0 at the moment. (this is part of our effort to upgrade) > > My first candidates are: > > -----internal commit message---- > Add support for dumping kernel dumps in addition to text dumps for > kernel panics. Add a new version of savecore to the tree, which knows > how to retrieve and save both dumps. Control the new dump behavior via the > debug.kerneldump_requested sysctl - disabling this wil go back to the > old text dump-only behavior. I wonder which would be more useful: this, or just dumping the full dump and using crashinfo to create a text summary after reboot. Of course, crashinfo could be enhanced to show anything it's currently missing (relative to the text dump). This would have the advantage of doing less stuff at dump time. Yours would have the advantage that it exists and works. :) Thoughts? > ------ part 2 ----- > Have savecore be more optimistic about > saving compressed cores - always try, and only bail if we actually run > out of space. The pessimistic "only try saving if we've got enough free > space to handle the entire dump uncompressed" made it too easy for us to > run out of space on our /var/crash partition Yes, please. I've run into this occasionally, but it never annoyed me enough to fix it. Procrastination pays off yet again. ;) Eric