Date: Wed, 26 Jan 2011 10:42:37 -0500 From: John Baldwin <jhb@freebsd.org> To: Ken Smith <kensmith@buffalo.edu> Cc: svn-src-projects@freebsd.org, Pawel Jakub Dawidek <pjd@freebsd.org>, Alexander Motin <mav@freebsd.org>, src-committers@freebsd.org, Robert Watson <rwatson@freebsd.org> Subject: Re: svn commit: r217828 - projects/graid/head/sys/geom/raid Message-ID: <201101261042.38218.jhb@freebsd.org> In-Reply-To: <1296054407.19051.5.camel@bauer.cse.buffalo.edu> References: <201101251534.p0PFY7cF039182@svn.freebsd.org> <4D3FED31.8040304@FreeBSD.org> <1296054407.19051.5.camel@bauer.cse.buffalo.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, January 26, 2011 10:06:47 am Ken Smith wrote: > On Wed, 2011-01-26 at 11:45 +0200, Alexander Motin wrote: > > Those who want maximum robustness should use dedicated > > drive on the most trivial dedicated controller to make dumping reliable. > > If we are going above that - there are always some compromises. > > Please remember this statement when I change dumpdev from "AUTO" > to "NO" in /etc/defaults/rc.conf shortly after branching stable/9. :-) No, I still think this is the wrong answer. Kernel dumps are not inherently unreliable to the point that we should not enable them by default. However, turning dumps off is a good way to prevent developers from debugging non- trivial bugs that are only triggered under real-world workloads. I think we should strive to make our dumps as reliable as possible, but nothing in our system is perfect (hence bugs), and if we are going to require absolute perfection for kernel dumps before enabling them by default then we might as well not ship anything at all as I can _ensure_ you the rest of the system we ship is _not_ absolutely perfect. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201101261042.38218.jhb>