From owner-freebsd-fs Sun Apr 1 17:34:14 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 4A82837B71A for ; Sun, 1 Apr 2001 17:34:10 -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 f320Y9w09139 for ; Sun, 1 Apr 2001 19:34:09 -0500 (CDT) (envelope-from kirk@honeypot.net) Received: from kirk by pooh.honeypot with local (Exim 3.12 #1 (Debian)) id 14jsHt-0000Ey-00 for ; Sun, 01 Apr 2001 19:33:41 -0500 To: freebsd-fs@freebsd.org Subject: Re: My Vinum heart attack References: <87vgooi7kz.fsf@pooh.honeypot> <20010402082816.J77617@wantadilla.lemis.com> From: Kirk Strauser Date: 01 Apr 2001 19:33:41 -0500 In-Reply-To: <20010402082816.J77617@wantadilla.lemis.com> Message-ID: <87g0fsi1i2.fsf@pooh.honeypot> Lines: 61 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-01T22:58:16Z, Greg Lehey writes: > > During the reboot-into-single-user > > process, I watched in abject horror as vinum started, tried to read > > its configuration, didn't like what it found, and TOTALLY WIPED > > everything in /dev/vinum (including subdirectories). > This is a feature, not a bug. Don't confuse a device node (in /dev) > with the device itself. I didn't suppose that it was a bug - just a nerve-wrecking response to a set of input data. > > After regaining consciousness, I realized that I had a live tape > > backup online, so I restored /dev/vinum, > You shouldn't have done that. What would've been the proper response? I don't have a log of the errors (/var/log/vinum_history has nothing, and neither does /var/log/messages), but they were along the lines of: Could not create /dev/vinum/plex - directory already exists or something very similar. The end result was an empty /dev/vinum. 'vinum list' gave a huge dump of invalid volumes, plexes, subdrives, and drives. > Well, if you had kept the log files, we could check. The only change > made to Vinum in that time was a minor one fixing a panic when > starting striped plexes. Take a look at > http://www.vinumvm.org/vinum/how-to-debug.html and let me know what > info you have. I'm sorry, Greg, but there were no log files to keep. The only scraps of possible interest were a backup of the resultant /dev/vinum directory: drwxr-xr-x 6 root wheel 512 Mar 31 16:29 . drwxr-xr-x 6 root wheel 15872 Mar 31 17:47 .. crw------- 1 root wheel 91, 0x40000001 Mar 31 16:26 Control crw------- 1 root wheel 91, 0x40000002 Mar 31 16:26 control crw------- 1 root wheel 91, 0x40000000 Mar 31 16:26 controld drwxr-xr-x 2 root wheel 512 Mar 31 16:26 drive drwxr-xr-x 2 root wheel 512 Mar 31 16:26 plex drwxr-xr-x 2 root wheel 512 Mar 31 16:26 sd drwxr-xr-x 3 root wheel 512 Mar 31 16:26 vol ./vol: total 3 drwxr-xr-x 3 root wheel 512 Mar 31 16:26 . drwxr-xr-x 6 root wheel 512 Mar 31 16:29 .. drw-r----x 2 root wheel 512 Mar 31 16:26 .plex ./vol/.plex: total 2 drw-r----x 2 root wheel 512 Mar 31 16:26 . drwxr-xr-x 3 root wheel 512 Mar 31 16:26 .. and a copy of vinum.core. Everything else was dumped to console, AFAIK. -- Kirk Strauser To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message