From owner-freebsd-stable Fri May 22 18:13:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04866 for freebsd-stable-outgoing; Fri, 22 May 1998 18:13:27 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA04843; Fri, 22 May 1998 18:13:13 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yd2NP-0005a4-00; Fri, 22 May 1998 17:41:31 -0700 Date: Fri, 22 May 1998 17:41:23 -0700 (PDT) From: Tom To: Eivind Eklund cc: Simon Shapiro , freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: DPT install problem In-Reply-To: <19980522213111.03467@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Fri, 22 May 1998, Eivind Eklund wrote: > On Fri, May 22, 1998 at 10:41:41AM -0700, Tom wrote: > > Yes, it seems to be a sysinstall interaction. If I leave the space > > unallocated, and then disklabel and newfs it later, it works fine. > > > > Currently it is pretty hard to bootstrap a new DPT system. You have to > > be able to build a kernel somewhere else as sysinstall will install a > > non-DPT kernel, and you can't use sysinstall to allocate large DPT > > partitions. I fear for the new user. > > sysinstall doesn't do this anymore. The DPT driver is activated as > part of the standard sysinstall now. I've noticed that. But this won't help anyone until 2.2.7 is released, or somone makes a 2.2.6 snapshot with the new GENERIC kernel. > As for large arrays: I think that will have to be left to you that > actually have those large arrays - it is kind of difficult for us > others to find out where the problem is. I suspect libdisk might be > the culprit; it interact with the slice code using different IOCTLs > than disklabel, IIRC. So you think that sysinstall makes a bogus label? Remember, sysinstall hangs basically right after newfs'ing the large filesystem. Either newfs hangs while cleaning up, or something that sysinstall does after newfs'ing all the filesystems hangs. Another interesting tibbit, is that sysinstall seems to be generating once a second disk i/o requests during this hung state. Could be stuck in loop. > Eivind. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message