From owner-freebsd-stable@FreeBSD.ORG Tue Jul 13 23:41:33 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0240F16A4CE; Tue, 13 Jul 2004 23:41:33 +0000 (GMT) Received: from smtp-gw-cl-c.dmv.com (smtp-gw-cl-c.dmv.com [216.240.97.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9176443D2F; Tue, 13 Jul 2004 23:41:32 +0000 (GMT) (envelope-from sven@dmv.com) Received: from mail-gw-cl-b.dmv.com (mail-gw-cl-b.dmv.com [216.240.97.39]) i6DNfV9D056235; Tue, 13 Jul 2004 19:41:31 -0400 (EDT) (envelope-from sven@dmv.com) Received: from [192.168.1.2] (dogpound.dyndns.org [64.45.134.154]) by mail-gw-cl-b.dmv.com (8.12.9/8.12.9) with ESMTP id i6DNfUnq018468; Tue, 13 Jul 2004 19:41:31 -0400 (EDT) (envelope-from sven@dmv.com) Message-ID: <40F4733A.5090400@dmv.com> Date: Tue, 13 Jul 2004 19:41:46 -0400 From: Sven Willenberger User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steve Shorter References: <20040711192909.GA70190@nomad.lets.net> <20040711211001.GZ14202@wantadilla.lemis.com> <20040713190845.GA74275@nomad.lets.net> In-Reply-To: <20040713190845.GA74275@nomad.lets.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.39 cc: FreeBSD Questions cc: FreeBSD Stable Users Subject: Re: serious vinum bug in 4-10 RELEASE?-solved? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jul 2004 23:41:33 -0000 Steve Shorter wrote: > On Mon, Jul 12, 2004 at 06:40:01AM +0930, Greg 'groggy' Lehey wrote: > >>I see no drives. >> >> >>> Ideas? >> > > I have concluded that this is the result of somekind > of vinum/hardware incompatibility. The problem in question > occured during the upgrade to faster disks, specifically, > Seagate Cheetah ST318453LC on a DELL 2450. If I swap back > the old Quantum Atlas 36G disk, the problem entirely > disappears. The new disks function ok with UFS partitions > but not vinum. It is 100% repeatable. > > Don't know why. > We have had issues with Cheetah U320 harddrives (at least the 10K 80-pin varieties on our Supermicro boxes) with a high percentage of drive failures ( > 10%) and communications errors across the scsi bus. These errors disappear when we reverted back to IBM/Hitachi drives. The Seagate issues occur with both FreeBSD 4.x and 5.x series so there is something in the Seagate firmware (I believe) that is interacting poorly with FreeBSD. We have experienced these issues with vinum setups and other configurations where the there are either multiple Seagate drives or multiple drives where one of them is a Seagate. Firmware updates did not help. I have not had this problem where there is only one drive and it occupies da0. Sven