From owner-freebsd-fs Tue May 15 7:36:35 2001 Delivered-To: freebsd-fs@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 8A99037B42C for ; Tue, 15 May 2001 07:36:33 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA39732; Tue, 15 May 2001 10:36:21 -0400 (EDT) (envelope-from wollman) Date: Tue, 15 May 2001 10:36:21 -0400 (EDT) From: Garrett Wollman Message-Id: <200105151436.KAA39732@khavrinen.lcs.mit.edu> To: Kris Kennaway Cc: fs@FreeBSD.org Subject: Re: [kris@obsecurity.org: Re: cvs commit: src/etc rc] In-Reply-To: <20010514202707.B93481@xor.obsecurity.org> References: <200105132342.QAA21879@beastie.mckusick.com> <200105142334.QAA05923@usr06.primenet.com> <20010515115630.H59553@wantadilla.lemis.com> <20010514193332.A85465@xor.obsecurity.org> <20010515120558.M59553@wantadilla.lemis.com> <20010514202707.B93481@xor.obsecurity.org> Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > unchanged), but there are exceptional cases where this is not true, > and applications will be started on a corrupted filesystem. > These exceptional cases will be detected in the background, at which If the corruption is significant and the filesystem is active, it will often (but not always) lead to a panic fairly quickly -- perhaps even before the background fsck has run. (Recall that the background fsck has to create a snapshot before it can do anything; it's possible that the process of creating the snapshot will trip over filesystem corruption and panic the system.) -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message