From owner-freebsd-stable@FreeBSD.ORG Wed Jul 6 21:22:42 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org 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 5649916A41C; Wed, 6 Jul 2005 21:22:42 +0000 (GMT) (envelope-from sven@dmv.com) 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 EE96B43D4C; Wed, 6 Jul 2005 21:22:41 +0000 (GMT) (envelope-from sven@dmv.com) Received: from lanshark.dmv.com (lanshark.dmv.com [216.240.97.46]) by smtp-gw-cl-c.dmv.com (8.12.10/8.12.10) with ESMTP id j66LMaYY075347; Wed, 6 Jul 2005 17:22:36 -0400 (EDT) (envelope-from sven@dmv.com) From: Sven Willenberger To: Ade Lovett In-Reply-To: <42CB8864.3010209@FreeBSD.org> References: <42B5ED53.3010805@hosting50.cz> <42C8F90D.3050505@cytexbg.com> <42CB8864.3010209@FreeBSD.org> Content-Type: text/plain Date: Wed, 06 Jul 2005 17:23:32 -0400 Message-Id: <1120685012.30350.38.camel@lanshark.dmv.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.39 Cc: freebsd-stable@freebsd.org Subject: Re: SCSI troubles X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2005 21:22:42 -0000 On Wed, 2005-07-06 at 00:29 -0700, Ade Lovett wrote: > Niki Denev wrote: > > From what i understand this is not exactly a FreeBSD problem, but rather > > a consequence of U320 being really hard on the hardware with pushing it > > to the limits. > > Incorrect. The relevant parts of the output you pasted are: > > ahd > Seagate drives > > Attaching more than one Seagate drive to a single Adaptec chain will > result in various weird and wonderful behavior as you've described. > > This is above and beyond well known (and documented) issues with data > loss and corruption with certain firmware revisions on Seagate drives. > > You have essentially two options: > > (1) disable the (on-board) adaptec controller, and use something else > (LSI cards work pretty good) > > (2) chunk the Seagate drives, and replace them with some other vendor > (Hitachi, for example, in our high-stress environments, show equivalent > MTBFs) > We went with option 2 about a year or so ago (Hitachi drives in our case) as dealing with Seagate on this issue turned into an exercise in frustration (they suggested things like turning off SMP or using a PCI network card instead of the onboard (em) network. As is pointed out the issue really crops up with more than one seagate drive on the adaptec (ahd) controller, even with the drives upated to their latest bios. Switching to a different hard drive manufacturer solved our woes. Sven