From owner-freebsd-stable@FreeBSD.ORG Fri Aug 27 19:04:42 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1211F16A4CE for ; Fri, 27 Aug 2004 19:04:42 +0000 (GMT) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16C0843D39 for ; Fri, 27 Aug 2004 19:04:41 +0000 (GMT) (envelope-from fbsd-stable@mawer.org) Received: from c211-30-90-140.belrs3.nsw.optusnet.com.au (c211-30-90-140.belrs3.nsw.optusnet.com.au [211.30.90.140]) i7RJ4dTp015693 for ; Sat, 28 Aug 2004 05:04:40 +1000 Received: (qmail 39745 invoked from network); 27 Aug 2004 19:04:39 -0000 Received: from unknown (HELO ?10.1.1.1?) (unknown) by unknown with SMTP; 27 Aug 2004 19:04:39 -0000 Message-ID: <412F85CC.5090806@mawer.org> Date: Sat, 28 Aug 2004 05:04:44 +1000 From: Antony Mawer User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pavel Merdine References: <1076237332.20040827215245@kaluga.ru> In-Reply-To: <1076237332.20040827215245@kaluga.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: ffs_alloc panic patch X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Aug 2004 19:04:42 -0000 Pavel Merdine wrote: > Panic is VERY undesirable situation. And I'm in doubt why those people > who wrote ffs like panics so devotedly: > > # grep -c "panic" ffs_alloc.c ffs_softdep.c > ffs_alloc.c:37 > ffs_softdep.c:108 > > I think such things are not acceptable in production environment. Why > those functions cannot just return a failure state and leave system > working? Taking a stab in the dark here, I'd suspect that this is a safety mechanism -- if something goes awry in the filesystem code, the implications could have something of a domino effect and wind up leaving you with a hosed filesystem. Rather than take that chance, the system panics, which attempts to minimising the impact the code could have on your filesystem(s) by otherwise continuing on. Someone correct me if I'm off-base here... Antony