From owner-freebsd-current Fri Apr 12 15:49: 3 2002 Delivered-To: freebsd-current@freebsd.org Received: from gypsy.vrac.iastate.edu (gypsy.vrac.iastate.edu [129.186.232.122]) by hub.freebsd.org (Postfix) with ESMTP id 5262737B41B for ; Fri, 12 Apr 2002 15:49:00 -0700 (PDT) Received: from 137.org (crow.vrac.iastate.edu [129.186.232.120]) by gypsy.vrac.iastate.edu (Postfix) with ESMTP id 5BBE113 for ; Fri, 12 Apr 2002 17:48:58 -0500 (CDT) Message-ID: <3CB763C5.8070200@137.org> Date: Fri, 12 Apr 2002 17:46:29 -0500 From: Patrick Hartling User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Vinum problems Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I suffered a system crash earlier today running -current from April 10. I have a Vinum volume set up as a mirror, and during the reboot, I had to fsck it. Everything seemed normal (at least that's what I thought), but now my volume cannot be mounted. The output from 'vinum list' is as follows: 2 drives: D a State: up /dev/da3s1e A: 0/12288 MB (0%) D b State: up /dev/da4s1e A: 0/12288 MB (0%) 1 volumes: V mirror State: down Plexes: 2 Size: 11 GB 2 plexes: P mirror.p0 C State: faulty Subdisks: 1 Size: 11 GB P mirror.p1 C State: faulty Subdisks: 1 Size: 11 GB 2 subdisks: S mirror.p0.s0 State: crashed D: a Size: 11 GB S mirror.p1.s0 State: crashed D: b Size: 11 GB The fact that it says the drives have 0% used greatly concerns me. Before I delve into this any further, is that a sign that everything I had is just gone? Or is there some hope of recovery? There is nothing in /var/log/vinum_hitsory or /var/log/messages that gives me any insight into what went wrong. -Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message