From owner-freebsd-stable Tue Jan 16 14:33:47 2001 Delivered-To: freebsd-stable@freebsd.org Received: from raffles-it.com (raffles.demon.co.uk [158.152.17.201]) by hub.freebsd.org (Postfix) with ESMTP id 50CE437B402 for ; Tue, 16 Jan 2001 14:33:28 -0800 (PST) Received: from dribble.lan.raffles-it.com (dribble.lan.raffles-it.com [192.168.100.50]) by raffles-it.com (8.11.1/8.11.1) with ESMTP id f0GMMB803353; Tue, 16 Jan 2001 22:22:11 GMT (envelope-from dpd@lan.raffles-it.com) Received: from dribble.lan.raffles-it.com (localhost [127.0.0.1]) by dribble.lan.raffles-it.com (8.11.1/8.11.1) with ESMTP id f0GMZXc09778; Tue, 16 Jan 2001 22:35:33 GMT (envelope-from dpd@lan.raffles-it.com) Message-Id: <200101162235.f0GMZXc09778@dribble.lan.raffles-it.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Andrew Gordon Cc: freebsd-stable@FreeBSD.ORG, dpd@dribble.lan.raffles-it.com Subject: Re: Vinum incidents. In-Reply-To: Message from Andrew Gordon of "Tue, 16 Jan 2001 15:23:40 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 16 Jan 2001 22:35:33 +0000 From: David Dooley Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew, I am afraid that I had the same problems with a Raid 5 vinum disk using 7 9GB Compaq/Segate drives. I created a 50GB volume for user home directories and it had very low traffic volumes. I managed to recover a stale drive on several occasions, but every couple of days it would go stale again. I have now moved the data from the Raid 5 Volume to another volume that is built with mirrored drives. I rebuilt the raid volume a several more times, made a file system on it and mounted it and that was it, after several days with no traffic to the drives no messages saying that there were any problems it still went stale. The system stayed up through out and nothing appeared in any logs that I could find. The annoying thing to me was that a different drive or combination of drives went stale each time so I couldn't pin the problem down to a drive. I did try alternate termination and cables with no luck. I even swapped the termination with a an identically configured system the same problem reappeared, but didn't move across the systems with the changed hardware so I don't think the problem is with the hardware. At some point I will follow Greg Lehey's web site requirements for trouble shooting and send the required info to him for analysis. Greg's web site is at http://www.vinumvm.org/vinum/how-to- debug.html David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message