From owner-freebsd-scsi Mon Aug 11 10:41:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA18580 for freebsd-scsi-outgoing; Mon, 11 Aug 1997 10:41:59 -0700 (PDT) Received: from sendero-ppp.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA18574 for ; Mon, 11 Aug 1997 10:41:56 -0700 (PDT) Received: (qmail 16219 invoked by uid 1000); 11 Aug 1997 17:42:12 -0000 Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 11 Aug 1997 10:42:12 -0700 (PDT) Organization: Atlas Telecom From: Simon Shapiro To: Tom Samplonius Subject: RE: DPT problem with new boot.flp Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Tom Samplonius; On 11-Aug-97 you wrote: ... > It seems that the problem is within sysinstall. I specified a 200MB > /usr and left the rest of the array unallocated, and sysinstall newfs'ed > it fine. With which DPT version? > Perhaps sysinstall is generating a bogus label when you specify large > filesystems. Larger than 4GB, I run into problems, at times, regardless of SCSI interface. > Are people actually using sysinstall from the boot floppy to set up > a system with a DPT? I do. Routinely :-) There are two possibilities for the problem: a. Sysinstall does not understand well enough things which are too big. b. Newfs issues a very dense burst of disk WRITE operations to the raw device. This can cause, on certain motherboards, invalid PCI bus transfers. If you use the sys/conf/i386/DPT config file as template to build a kernel, this kernel will either resist, or report, or cope with this problem, or all of the above. The cost is in performance. Not terrible, but some cost. Simon