From owner-freebsd-fs Mon Apr 2 6:28:46 2001 Delivered-To: freebsd-fs@freebsd.org Received: from kanga.honeypot.net (kanga.honeypot.net [216.224.193.50]) by hub.freebsd.org (Postfix) with ESMTP id E080E37B71C for ; Mon, 2 Apr 2001 06:28:40 -0700 (PDT) (envelope-from kirk@honeypot.net) Received: from pooh.honeypot (mail@pooh.honeypot [10.0.1.2]) by kanga.honeypot.net (8.11.3/8.11.3) with ESMTP id f32DSeN07659 for ; Mon, 2 Apr 2001 08:28:40 -0500 (CDT) (envelope-from kirk@honeypot.net) Received: from kirk by pooh.honeypot with local (Exim 3.12 #1 (Debian)) id 14k4Nr-0000QV-00 for ; Mon, 02 Apr 2001 08:28:39 -0500 To: freebsd-fs@freebsd.org Subject: Re: My Vinum heart attack References: <87vgooi7kz.fsf@pooh.honeypot> From: Kirk Strauser Date: 02 Apr 2001 08:28:38 -0500 In-Reply-To: Message-ID: <878zljmnw9.fsf@pooh.honeypot> Lines: 22 X-Mailer: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 2001-04-02T13:12:37Z, Dag-Erling Smorgrav writes: > There is no critical information in /dev/vinum. The information there can > easily be recreated by vinum(8) from the configuration information stored > on the disks themselves. I wasn't too sure at the time which information was canonical - the copy in /dev/vinum, or the on-disk copy - so I wanted to be darn sure not to lose more than I needed to. Your point that it is easily recreated is true, given that vinum works at all in a particular situation. Mine didn't. I know why it didn't, and I managed to work through it without loss, but it certainly got my attention at the time. BTW, my note was much more a warning to others to pay attention to these things than a complaint. Vinum is a complicated thing, and you have to be willing to rise to the occasion if you want to use it, and I'm comfortable with that. -- Kirk Strauser To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message