From owner-freebsd-stable Sun Mar 5 18:31: 5 2000 Delivered-To: freebsd-stable@freebsd.org Received: from darius.concentric.net (darius.concentric.net [207.155.198.79]) by hub.freebsd.org (Postfix) with ESMTP id 8954837B794; Sun, 5 Mar 2000 18:30:59 -0800 (PST) (envelope-from aronchick@archegenesis.com) Received: from mcfeely.concentric.net (mcfeely.concentric.net [207.155.198.83]) by darius.concentric.net (8.9.1a/(98/12/15 5.12)) id VAA07264; Sun, 5 Mar 2000 21:30:57 -0500 (EST) [1-800-745-2747 The Concentric Network] Received: from aronchick (w148.z208036085.nyc-ny.dsl.cnc.net [208.36.85.148]) by mcfeely.concentric.net (8.9.1a) id VAA24376; Sun, 5 Mar 2000 21:30:56 -0500 (EST) Date: Sun, 05 Mar 2000 21:30:55 -0500 From: David Aronchick Reply-To: David Aronchick To: freebsd-scsi@FreeBSD.ORG Cc: freebsd-stable@FreeBSD.ORG Subject: Vinum vs Adaptec AIC 7890? Message-ID: <3104082854.952291855@aronchick> X-Mailer: Mulberry/2.0.0b11 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi-- I've had the following problems... we're currently running with 3x18 GB 10k Segate drives and an Asus p2b-ds with onboard scsi card. The drives are divided into 3 partitions /usr /var / and a RAID 5 of 26 GB. I was able to recover by just doing vinum start on the stale drive, but it brought the system down, and i need to make sure this doesn't happen again. Does anyone have any suggestions? Is this a CAM or vinum problem? or should I look to hardware. Here's the standard list. What problems are you having? Using lftp, I was in the midst of ftping a 50 MB or so file to the raid directly. After about 5% was done, the entire box froze. As it is remote, I don't know if the drives were accessing, but all open ssh sessions just stopped, i could ping and nmap the box, but when I tried to initiate an ssh, they would just open, and sit there. I've previously been able to copy a couple of hundred MB back and forth, with seemingly no problems. That was a few days ago. Which version of FreeBSD are you running? > uname -r 3.4-STABLE Have you made any changes to the system sources, including Vinum? No, everything is unchanged. Kernel stuff: # vinum list Configuration summary Drives: 3 (4 configured) Volumes: 1 (4 configured) Plexes: 1 (8 configured) Subdisks: 3 (16 configured) D d0 State: up Device /dev/da0s2e Avail: 311/15311 MB (2%) D d1 State: up Device /dev/da1s2e Avail: 311/15311 MB (2%) D d2 State: up Device /dev/da2s2e Avail: 311/15311 MB (2%) V raid5 State: up Plexes: 1 Size: 29 GB P raid5.p0 R5 State: degraded Subdisks: 3 Size: 29 GB S raid5.p0.s0 State: up PO: 0 B Size: 14 GB S raid5.p0.s1 State: stale PO: 512 kB Size: 14 GB S raid5.p0.s2 State: up PO: 1024 kB Size: 14 GB # tail -100 /var/log/messages [...] Mar 5 13:25:18 db /kernel: (da1:ahc0:0:1:0): READ(10). CDB: 28 0 0 41 82 4e 0 0 80 0 Mar 5 13:25:18 db /kernel: (da1:ahc0:0:1:0): MEDIUM ERROR info:41825b asc:11,0 Mar 5 13:25:18 db /kernel: (da1:ahc0:0:1:0): Unrecovered read error field replaceable unit: e4 sks:80,101 Mar 5 13:25:18 db /kernel: raid5.p0.s1: fatal read I/O error Mar 5 13:25:18 db /kernel: vinum: raid5.p0.s1 is crashed by force Mar 5 13:25:18 db /kernel: vinum: raid5.p0 is degraded Mar 5 13:25:18 db /kernel: raid5.p0.s1: fatal write I/O error Mar 5 13:25:18 db /kernel: vinum: raid5.p0.s1 is stale by force Mar 5 16:52:08 db /kernel: Copyright (c) 1992-1999 FreeBSD Inc. [ the machine was manually rebooted 3 hours later ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message