From owner-freebsd-questions Fri Jun 22 18:26:45 2001 Delivered-To: freebsd-questions@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 5474D37B406 for ; Fri, 22 Jun 2001 18:26:41 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id D51B26ACBC; Sat, 23 Jun 2001 10:56:38 +0930 (CST) Date: Sat, 23 Jun 2001 10:56:38 +0930 From: Greg Lehey To: Alexey Koptsevich Cc: questions@freebsd.org Subject: Re: starting vinum subdisk Message-ID: <20010623105638.C41017@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from kopts@astro.ioffe.rssi.ru on Fri, Jun 22, 2001 at 02:17:23PM +0400 Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 On Friday, 22 June 2001 at 14:17:23 +0400, Alexey Koptsevich wrote: > > Hello, > > I have a vinum one-plex two-subdisks striped volume. One bad block > occurred on one of the drives. After reassigning it from SCSI BIOS I had > the whole plex 'corrupt', one of its subdisks 'up' and another one > 'stale'. I have tried to 'start' the latter one, but this command hung, > and 'stale' switched to 'R 0%'. > > Is it possible to make the second subdisk 'up' somehow? Since the only bad > block has occurred almost all information there is accessible. I hope fsck > is able to revive the filesystem if the bad block resides in the data > area. If bad block resides in the vinum configuration area, maybe it is > possible to restore the second disk using configuration information from > the first one -- (both subdisks have equal sizes)? Unless it is not > possible with conventional methods, maybe it is possible to do it via > direct editing? You don't say what revision of FreeBSD you're running. I recently added the keyword "retryerrors" to subdisk configuration. You don't have this, and your system is not redundant, so the "correct" answer is to say "sorry, you've lost a subdisk". I'm rethinking this view, however. In the meantime you should be able to use the 'setstate' command to work around the problem: vinum -> setstate up vol.p0.s1 vol.p0.s0 vinum -> saveconfig Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message