From owner-freebsd-scsi Mon Oct 11 11:51:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 22A7B155E5 for ; Mon, 11 Oct 1999 11:51:24 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id UAA20074; Mon, 11 Oct 1999 20:50:45 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.3/8.9.1) id UAA60269; Mon, 11 Oct 1999 20:41:58 +0200 (MET DST) (envelope-from j) Message-ID: <19991011204158.08819@uriah.heep.sax.de> Date: Mon, 11 Oct 1999 20:41:58 +0200 From: J Wunsch To: patl@phoenix.volant.org Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Disktab entry for Seagate ST-19171W (Barracuda 9) Reply-To: Joerg Wunsch References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from patl@phoenix.volant.org on Sun, Oct 10, 1999 at 01:08:10AM -0700 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As patl@phoenix.volant.org wrote: > The symptom I'm getting is parity errors near the end of the newfs > on any reasonably large partition. That's hardly an error you could expect to be fixed by using another disktab entry. (Btw., disktab should probably completely go away.) Parity errors heavily smell like a cabling problem, which becomes more apparent when you drive the bus at full speed, while the host adapter formatting probably runs at a lower speed. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message