Date: Sat, 8 Mar 2003 20:03:41 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: Thomas Seck <tmseck-lists@netcologne.de> Cc: freebsd-current@FreeBSD.ORG Subject: Re: "blockable sleep lock" panic in latest -current. Message-ID: <20030308194529.W9775-100000@gamplex.bde.org> In-Reply-To: <20030306185709.1088.qmail@laurel.tmseck.homedns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030308194529.W9775-100000>