From owner-freebsd-questions@FreeBSD.ORG Thu Apr 1 12:46:53 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBE6516A4CE for ; Thu, 1 Apr 2004 12:46:53 -0800 (PST) Received: from relay04.roc.ny.frontiernet.net (relay04.roc.ny.frontiernet.net [66.133.131.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1ACBD43D2F for ; Thu, 1 Apr 2004 12:46:53 -0800 (PST) (envelope-from drew@mykitchentable.net) Received: (qmail 20988 invoked from network); 1 Apr 2004 20:46:52 -0000 Received: from 67-51-124-168.dsl1.elk.ca.frontiernet.net (HELO blacklamb.mykitchentable.net) ([67.51.124.168]) (envelope-sender )SMTP for ; 1 Apr 2004 20:46:52 -0000 Received: from mykitchentable.net (lugalong.mykitchentable.net [192.168.1.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by blacklamb.mykitchentable.net (Postfix) with ESMTP id A677A3BF36A; Thu, 1 Apr 2004 12:46:50 -0800 (PST) Message-ID: <406C7FC1.4060106@mykitchentable.net> Date: Thu, 01 Apr 2004 12:46:57 -0800 From: Drew Tomlinson User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD Questions References: <406C7853.6070009@mykitchentable.net> In-Reply-To: <406C7853.6070009@mykitchentable.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit cc: grog@FreeBSD.org Subject: Re: Vinum Subdisk Crashed - How To Repair? -- SOLVED!!! X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Apr 2004 20:46:53 -0000 On 4/1/2004 12:15 PM Drew Tomlinson wrote: > --- Greg 'groggy' Lehey wrote: > >>> On Friday, 26 March 2004 at 21:53:44 -0800, Drew >>> Tomlinson wrote: >> >> >>>> > Please excuse whatever format in which this email >>>> > arrives. My system is unusable so I am posting >>>> > from Yahoo!. >>> > > Thank you very much for your reply. I’ve tried to > clean this up so it remains readable when it reaches > you. > >>> Heh. I suppose that's a good enough reason. >> >>>> > I have a 4.9-RELEASE-p4 system. I have not made >>>> > any changes to any source code. I have 3 vinum >>>> > volumes configured. While attempting to diagnose >>>> > problems with one of the volumes that uses a >>>> > firewire drive, my system crashed with a trap >>>> > 12 error. I have my /usr configured as a > striped vinum volume >>>> with one plex and two > subdisks. Upon reboot, the usr volume has one >>>> > subdisk in a >>>> > crashed state. Thus I can't mount /usr and > can't get my system >>>> up and running. >>>> > >>>> > I *REALLY* don't want to lose my data on /usr >>>> > as I don't have a backup. It was my backup >>>> > volume problems I was looking at when my >>>> > trouble started. I have looked at >>>> > http://www.vinumvm.org/vinum/how-to-debug.html. I >>>> > have a copy of my config files and the page >>>> > says one can use those to recreate his >>>> > config without losing data as it does not write to >>>> > the subdisks. Is this what I should do? >>> >>> >>> Maybe. >> Not knowing what else to do, I totally removed everything related to my usr volume. Explicitly, I removed all subdisks, plexes, volumes, and drives, using the -f option when needed. Then I recreated the drives, volumes, plexes, and subdisks using my original configuration file. I was then able to fsck the volume and subsequently mount it. After this success, I repeated the steps on my ftp volume. One final reboot and the system came up and all my data appears to be there on both my usr and ftp volumes. Based upon this experience with vinum and a similar one I had last year around this time, I strongly suggest that one does not use vinum with firewire drives. I have one 80 GB IDE drive that is in a firewire enclosure. Upon reboot, the drive is not recognized by the system. Then when vinum tries to access it, vinum responds unpredictably because it's not there. Sometimes only the volume containing the missing disk is affected but other times, some or all vinum volumes are affected. I plan on writing up my experience with firewire to see if I'm doing something wrong or if there is some bug in the firewire driver in a new thread. Hopefully this post will prevent someone else from having the problems I've had. Drew