From owner-freebsd-current Sat Mar 8 1: 3:56 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBC3E37B401 for ; Sat, 8 Mar 2003 01:03:55 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83A3B43FBF for ; Sat, 8 Mar 2003 01:03:54 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id UAA13414; Sat, 8 Mar 2003 20:03:42 +1100 Date: Sat, 8 Mar 2003 20:03:41 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Thomas Seck Cc: freebsd-current@FreeBSD.ORG Subject: Re: "blockable sleep lock" panic in latest -current. In-Reply-To: <20030306185709.1088.qmail@laurel.tmseck.homedns.org> Message-ID: <20030308194529.W9775-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 6 Mar 2003, Thomas Seck wrote: > * Bruce Evans (bde@zeta.org.au): > > > This is the usual panic from sync() in panic() tripping over a lock. > > Calling sync() in panic was never safe and now usually fails. > > Should one set "kern.sync_on_panic" to zero then? Not a bad idea. It depends on whether you have good backups and UPS's I guess. Power failures give much the same loss and corruption of data and metadata as not syncing in panics (perhaps better since there is less chance of writing corrupt data; perhaps worse since dumping in panic() works better than syncing so the data is usually not lost irrecoverably after a panic with no sync). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message