Date: Wed, 16 Jan 2002 23:28:23 +0300 (MSK) From: Alexey Zakirov <frank@agava.com> To: <freebsd-stable@freebsd.org> Subject: vinum behavior after disk errors Message-ID: <Pine.BSF.4.32.0201162328090.11967-100000@hellbell.domain>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.32.0201162328090.11967-100000>