From owner-freebsd-fs Wed Oct 27 19: 4:53 1999 Delivered-To: freebsd-fs@freebsd.org Received: from calis.blacksun.org (Calis.blacksun.org [168.100.186.40]) by hub.freebsd.org (Postfix) with ESMTP id 9A86914CC3 for ; Wed, 27 Oct 1999 19:04:50 -0700 (PDT) (envelope-from don@calis.blacksun.org) Received: from localhost (don@localhost) by calis.blacksun.org (8.9.3/8.9.2) with ESMTP id WAA36097; Wed, 27 Oct 1999 22:06:30 -0400 (EDT) (envelope-from don@calis.blacksun.org) Date: Wed, 27 Oct 1999 22:06:30 -0400 (EDT) From: Don To: Greg Lehey Cc: Bernd Walter , Alfred Perlstein , freebsd-fs@FreeBSD.ORG Subject: Re: Journaling In-Reply-To: <19991027173720.06226@mojave.worldwide.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Ok nevermind :) Either way vinum is not up to snuff. It still has a way to > > go before it can be used in a production environment. > > Oh, does it? What problems have you seen? You'd better tell all the > people who are using it in production, too. Perhaps you should read the vinum known bugs page. That list is far too long for a production application. If you dont feel it is too long then by all means use it. When I stop seeing the words "data corruption" and "kernel panic" on the known bugs page then I will use vinum. -don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message