From owner-freebsd-current Sun Jul 23 19: 3:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 85FA837B5A8; Sun, 23 Jul 2000 19:03:25 -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 WAA98524; Sun, 23 Jul 2000 22:03:23 -0400 (EDT) (envelope-from wollman) Date: Sun, 23 Jul 2000 22:03:23 -0400 (EDT) From: Garrett Wollman Message-Id: <200007240203.WAA98524@khavrinen.lcs.mit.edu> To: boshea@ricochet.net Cc: Kris Kennaway , Joe McGuckin , james@targetnet.com, freebsd-current@FreeBSD.ORG Subject: Re: Re[2]: Journaling Filesystem ? In-Reply-To: <20000723173124.C351@beastie.localdomain> References: <200007232043.NAA36306@monk.via.net> <20000723173124.C351@beastie.localdomain> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I didn't even know that background fsck was supported at all. I > remember hearing Kirk talk about it as a future feature at FreeBSD CON > last year, but I havn't heard anything about it since. How do you > use it? It is not quite there yet. It requires the snapshot code, which just recently made its way into the tree, and some new system calls to inform the filesystem that block X is actually free. However, this doesn't change the fact that fsck is not required in order to ensure correct operation after a crash. Depending on your access patterns, the block and inode leakage may be small enough to not matter. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message