From owner-freebsd-hackers@freebsd.org Thu Jul 12 14:50:13 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F23D1040FD8 for ; Thu, 12 Jul 2018 14:50:13 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A24CF953BD for ; Thu, 12 Jul 2018 14:50:12 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 5FB621040FD6; Thu, 12 Jul 2018 14:50:12 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AFFD1040FD4 for ; Thu, 12 Jul 2018 14:50:12 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 96540953B9; Thu, 12 Jul 2018 14:50:11 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x230.google.com with SMTP id a134-v6so24476151lfe.6; Thu, 12 Jul 2018 07:50:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=UJdNtD8N0DReTCseOdc04esOhY6RY+cfzCprI+1IME4=; b=H/18WJZ/HJ/PSKPVxWE7NFhnylnTd+FzE27twR+v25ibe3OuW9HNN6tFy8o3FMN5U6 VUucQptvBXdxG0qUEQhMEeYqXZMXJgQckLOmz7PAJvi9tYErVwgrD0hp8EEi40VSSpQo 8ebDMn0ERtYS67+b7WYDabGstMKeBwiZ31YaXEbZvWwwg6eLrBnsNna18wMNgBnkTCfh mXZG0iroGvL0CTp69x57l4dlVqzLHG9cYNhqzHWrq1AyILkijVCUqtBLmJPNgBf5O8Gr Po+hlwNizxRZCn7aiURs/eWckGksYPtNJJ941ji8Vzj7DUqOn2mz6Lzs8ELG0z3R1zMu k9Gg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=UJdNtD8N0DReTCseOdc04esOhY6RY+cfzCprI+1IME4=; b=G9VgPff+7RHFIRbW0ti6TWZSLJgkk9Fp7Ys9lWF5cm0JKQKnS4OVud2OIszEhr/8yo ZhewoLq71BQZG7S5WkcFQRwt5kHqDvRu2bW0ol80nYFtRTC6t34RicPSN6GbhIZk7917 sQzbOo5a+SCbaF0Wq5bDQGeINLiDuyvpSLyevV1dPgN7IP7IGK8JTG/1mAHJiKCfkaJN SDa/3fTQcvFmvrL6un3DZMXYnzYVj3NWgSfU1zewEvuZmrA4HBsGlAMqXi20+ZUvlTYr 5vvuIdAtIc0q5pT5twFmdmb8gnaAfuNq/Nndt03gH4NtcUcRuz+4kQrznD7cyXtYbb9G x+Xw== X-Gm-Message-State: AOUpUlE29Ap0fGCBfJUL2Vni+1FTQISPeNEA1fCmaSlnZXUhqs4f40zE VArE5CvT4dnL+3QzI5zHci2cZUzXXdyZa9KkQLo= X-Google-Smtp-Source: AAOMgpferAaSnio3VdDNzxa0LqV0Q3YFn8YzfAYlZUw+pxviVr09CoqoQv/pVzKxpQg7wjE4WswS9vorgmgTRipFlF8= X-Received: by 2002:a19:c004:: with SMTP id q4-v6mr2098073lff.16.1531407009200; Thu, 12 Jul 2018 07:50:09 -0700 (PDT) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 2002:ab3:1b91:0:0:0:0:0 with HTTP; Thu, 12 Jul 2018 07:50:08 -0700 (PDT) In-Reply-To: <20180712143118.GA15892@raichu> References: <20180712141409.Horde.NVSzLsvqE-2PCSDqhhfb0Xd@webmail.leidinger.net> <20180712143118.GA15892@raichu> From: Alan Somers Date: Thu, 12 Jul 2018 08:50:08 -0600 X-Google-Sender-Auth: 5yQ1JpJhhhkOGBDpwQmHTvY5yCk Message-ID: Subject: Re: crashinfo doesn't support compressed crashdumps - which way forward? To: Mark Johnston Cc: Alexander Leidinger , "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2018 14:50:13 -0000 On Thu, Jul 12, 2018 at 8:31 AM, Mark Johnston wrote: > On Thu, Jul 12, 2018 at 02:14:09PM +0200, Alexander Leidinger wrote: > > Hi, > > > > the crashinfo script doesn't know how to handle compressed coredumps. > > What would be acceptable behavior (ordered by my preferrence)? > > 1) decompress in /var/crash and then proceed normally (already > > implemented locally) > > 2) decompress to CRASHTMPDIR:/var/tmp/xxx and delete when finished > > 3) keep it like it is > > 4) teach tools to understand compressed dumps (gzip / zstd) > I briefly looked into this option, but it's harder than it sounds. There are several libraries that would need to be modified, and I think some of them work by mmap(2)ping the core file rather than by fread(2)ing it. I don't know of anyway to mmap a compressed file. > > > > Implicitly there is the question what what is the purpose of > > compressing crashdumps, to have more RAM than space in dumpdev (which > > is valid in my case), or to save space in /var/crash (which I don't > > care much about). > Compressed crashdumps are also great for systems with slow dumpdevs. They greatly speed up the dumping process. > > I think jhb has a patch which implements 2). I do not have strong > feelings on which is the right way forward, but I mildly prefer 2) to > 1). It looks like crashinfo can be disabled in rc.conf, so users who > are space-constrained in /var/crash can take the additional step of > setting crashinfo_enable=NO. FWIW, when I committed the compression > support, my use-case involved both a small dump device and a small > /var filesystem. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >