From owner-freebsd-current Thu Jul 23 20:48:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02816 for freebsd-current-outgoing; Thu, 23 Jul 1998 20:48:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA02801 for ; Thu, 23 Jul 1998 20:48:12 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yzYpZ-0005iF-00; Thu, 23 Jul 1998 20:47:41 -0700 Date: Thu, 23 Jul 1998 20:47:38 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: Doug White cc: Lee Reese , current@FreeBSD.ORG Subject: Re: Viability of -current for Usenet News In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Jul 1998, Doug White wrote: > On Thu, 23 Jul 1998, Tom wrote: > > > > > I've just seen a RedHat 5.1 system with a such a controller, hang. It > > > > doesn't seem the Linux DPT driver is very stable. It seems easy to get > > > > into a situation where all processes accessing the disk, hang. The > > > > FreeBSD DPT driver seems quite a bit more solid than that, although > > > > setting it up is more difficult. > > > > > > Not really anymore, apparently the 2.2.7 boot floppy now has the driver > > > built on it (yay!). > > > > Yes, but sysinstall bugs will probably force you to do most of the > > filesystem setup manually. See archives. > > &#@^! ... In what list? It hasn't hit the archives and I haven't seen > anything yet. This has gone for almost a year. Talked about in frebsd-scsi for sure, and probably freebsd-stable. Basically what happens, is that sysinstall hangs just after newfs'ing the filesystems. The work around is to leave most of the space unallocated, and label it and newfs after booting. Again a very old problem going back to Novemeber or so last year. There has been speculation that since sysinstall uses libdisk, not disklabel to write labels, that the problem might be in the disklabels created by sysinstall on a DPT array, caused by the size and/or geomentry of the DPT array (all the DPT arrays I've under FreeBSD tickled this bug, and all very 16GB or bigger). > Doug White | University of Oregon > Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant > http://gladstone.uoregon.edu/~dwhite | Computer Science Major Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message