From owner-freebsd-questions Fri Aug 17 11:36:51 2001 Delivered-To: freebsd-questions@freebsd.org Received: from central.pathlink.com (mktg-3.pathlink.com [209.155.56.203]) by hub.freebsd.org (Postfix) with ESMTP id 6E93137B40E for ; Fri, 17 Aug 2001 11:36:41 -0700 (PDT) (envelope-from rich@central.pathlink.com) Received: from mktg-2.central.pathlink.com (mktg-2.pathlink.com [209.155.56.202]) by central.pathlink.com (8.11.1/8.11.1) with ESMTP id f7HIaZY75564 for ; Fri, 17 Aug 2001 11:36:35 -0700 (PDT) (envelope-from rich@central.pathlink.com) Message-Id: <4.3.2.7.2.20010817105133.00a91100@127.0.0.1> X-Sender: (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 17 Aug 2001 11:37:07 -0700 To: freebsd-questions@FreeBSD.ORG From: Rich Subject: Vinum recovery (input/output error on a stripe) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I ran into an odd error this morning with a vinum configuration (FreeBSD V4.0 CD install) and wasn't sure if I could correct it. About a year or so back I installed two scsi drives as a stripe and had been working fine. The system has three drive, one for "/" and the stripe mounted on /var. I have vinum setup to start up in my /etc/rc.conf file. I was getting an input/output error on the stripe. I ran a hardware check on the two scsi drives and wasn't seeing any errors for them so those looked like they checked out okay. When I boot into single user mode I ran a "mount -a" and got a "mount: Input/output error" message. The stripe is the only other file system I have setup to mount automatically in /etc/fstab. I tried running fsck on /dev/vinum/mystripe but it wasn't seeing that as a freebsd file system. I can load vinum but when I try to start it gave me an error... P mystripe.p0 S State: corrupt Subdisks: 2 Size 16 GB S mystripe.p0.s0 State: stale PO: 0 B Size 8360 MB I had originally create this configuration for vinum drive d1 devise /dev/da1s1e drive d2 devise /dev/da1s2e volume mystripe plex org striped 512k sd length 0 drive d1 sd length 0 drive d2 When I use a "list -v" in vinum I get the following (summarized). Looked like the plex was corrupt and the first drive was stale... Drive d1: Device /dev/da1s1e Size 8361 MB State: up Last error: none Drive d2: Device /dev/da2s1e Size 8361 MB State: up Last error: none 1 volumes Volume mystripe Size 16721 MB State: up Flags 1 plexes Read policy: round robin 1 plexes Plex mystripe.p0: Size 16721 MB Subdisks: 2 State corrupt Organization: striped Strip size: 512 kb Part of volume mystripe 2 subdisks: Subdisk mystripe.p0.s0 Size 8360 MB State: stale Plex mystripe.p0 at offset 0 B Drive d1 (/dev/da1s1e) at offset 132 kb Subdisk mystripe.p0.s1 Size 8360 MB State: up Plex mystripe.p0 at offset 512 kb Drive d2 (/dev/da2s1e) at offset 132 kb If the drives were okay but the plex is corrupt, is the data recoverable? I wasn't able to run the "vinum dumpconfig" command, but sounds like I might need to run "resetconfig". I do have my original config file available. If so would I run that as "resetconfig /path/to/configfile". Thanks, Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message