Date: Wed, 22 Sep 2010 17:15:25 -0400 From: Ken Smith <kensmith@buffalo.edu> To: Andriy Gapon <avg@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, Gavin Atkinson <gavin@freebsd.org>, src-committers@freebsd.org, John Baldwin <jhb@freebsd.org> Subject: Re: svn commit: r212964 - head/sys/kern Message-ID: <4C9A71ED.6020406@buffalo.edu> In-Reply-To: <4C9A6EE6.5050301@freebsd.org> References: <201009211507.o8LF7iVv097676@svn.freebsd.org> <4C9A1602.4020204@freebsd.org> <1285169017.64197.29.camel@buffy.york.ac.uk> <201009221558.27393.jhb@freebsd.org> <4C9A6EE6.5050301@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 9/22/10 5:02 PM, Andriy Gapon wrote:
> on 22/09/2010 22:58 John Baldwin said the following:
>
>> Agreed. FWIW, I actually think that this is the only change needed as
>> crashinfo is enabled by default in 8.x and later. We already include symbols
>> in kernels by default now, so just setting dumpdev will give you the same
>> info you generally can get from a textdump in the form of a simple
>> /var/crash/core.txt.N file.
>>
>> The other benefit of full crashdumps + crashinfo as compared to textdumps is
>> that a developer can request further information in a PR followup (fire up
>> kgdb and enter command 'X' and reply with the output). With a textdump any
>> info not collected by the textdump is lost once the machine reboots after the
>> crash.
>
> Agree++
> But what was the reason that dumpdev="AUTO" was reverted?
> I remember that POLA was quoted at the time.
> I am not sure what the astonishment actually was - perhaps 'AUTO' was not smart
> enough and destroyed somebody's data?
>
Not everybody would notice /var getting full of crash dumps.
Picture a server farm where for the most part the machines
are all just plain on auto-pilot. If one or several develop
a problem that causes panic's /var can become full and possibly
cause the machine to stop doing something important (between
panic's...). I wasn't around when the initial decision for
what to have it set to was made but this was the reason for
me starting to do it again when I realized I forgot to at
least once, and hence the reference to POLA.
Crash dumps are good for individual workstations. Crash
dumps are good for servers *if* the admin knows they're
having a problem and is actively working on that server
to resolve the issue. But they're no so good and can
cause nasty side-effects if they're happening on a machine
not being watched over closely. That's the reason for
the change in setting when a -stable branch gets started.
- --
Ken Smith
- - From there to here, from here to | kensmith@buffalo.edu
there, funny things are everywhere. |
- Theodore Geisel |
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkyace0ACgkQ/G14VSmup/bfKwCdGWyWxuG91GSss6q3MUFAPi2r
6iwAmgLxxEXEODYubhfOFGkzwNx9r/Au
=IIBd
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C9A71ED.6020406>