From owner-freebsd-stable  Wed Jan 16 12:28:29 2002
Delivered-To: freebsd-stable@freebsd.org
Received: from relay2.agava.net.ru (ofc.agava.net [217.106.235.141])
	by hub.freebsd.org (Postfix) with ESMTP id A390C37B419
	for <freebsd-stable@freebsd.org>; Wed, 16 Jan 2002 12:28:25 -0800 (PST)
Received: from hellbell.domain (hellbell.domain [192.168.1.12])
	by relay2.agava.net.ru (Postfix) with ESMTP id 0729166B72
	for <freebsd-stable@freebsd.org>; Wed, 16 Jan 2002 23:28:24 +0300 (MSK)
Received: from localhost (localhost [127.0.0.1])
	by hellbell.domain (Postfix) with ESMTP id F08C7CD11
	for <freebsd-stable@freebsd.org>; Wed, 16 Jan 2002 23:28:23 +0300 (MSK)
Date: Wed, 16 Jan 2002 23:28:23 +0300 (MSK)
From: Alexey Zakirov <frank@agava.com>
X-X-Sender:  <frank@hellbell.domain>
To: <freebsd-stable@freebsd.org>
Subject: vinum behavior after disk errors
Message-ID: <Pine.BSF.4.32.0201162328090.11967-100000@hellbell.domain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-stable.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-stable>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-stable>
X-Loop: FreeBSD.ORG

	Hail!

I have a question about vinum behavior after some disk errors.
One of my servers sometimes have a glitch with the disk (or probably
controller). It's looks like this:

Jan 16 18:29:15 glance /kernel: (da0:sym0:0:0:0): phase change 2-7
10@13d44d68 resid=3.
Jan 16 18:29:15 glance /kernel: (da0:sym0:0:0:0): READ(10). CDB: 28 0 0 96
c1 6a 0 0 4 0
Jan 16 18:29:15 glance /kernel: (da0:sym0:0:0:0): ILLEGAL REQUEST asc:24,0
Jan 16 18:29:15 glance /kernel: (da0:sym0:0:0:0): Invalid field in CDB
field replaceable unit: 1 sks:ce,5

So vinum immediatly marks the plex as faulty:

Jan 16 18:29:15 glance /kernel: vinum: vinum0.p0.s0 is crashed by force
Jan 16 18:29:15 glance /kernel: vinum: vinum0.p0 is faulty
Jan 16 18:29:15 glance /kernel: vinum: vinum0 is down
Jan 16 18:29:15 glance /kernel: fatal:vinum0.p0.s0 read error, block
4048549 for 2048 bytes
Jan 16 18:29:15 glance /kernel: vinum0.p0.s0: user buffer block 4048284
for 2048 bytes

After reboot OS can't start because it can't check a vinum volume.
One must manually do "vinum start vinum0.p0" to get system up.

Is there any way to do something like 'fsck_y_enable="YES"' does?
Or should I patch /etc/rc to do "vinum start <my_plex>" after "vinum
start" ?

*** WBR, Alexey Zakirov (frank@agava.com)



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message