From owner-freebsd-stable Fri May 22 16:17:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11141 for freebsd-stable-outgoing; Fri, 22 May 1998 16:17:11 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero.simon-shapiro.org.142.69.207.in-addr.arpa [207.69.142.25] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA11113 for ; Fri, 22 May 1998 16:17:05 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 4104 invoked by uid 1000); 23 May 1998 00:18:15 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 22 May 1998 20:18:15 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Tom Subject: RE: DPT install problem Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On 22-May-98 Tom wrote: > > On Fri, 22 May 1998, Simon Shapiro wrote: > >> >> On 21-May-98 Tom wrote: >> > >> > I'm trying to use the boot-dpt 2.2.6-RELEASE floppy to bootstrap a >> > new >> > DPT based system. However, sysinstall hangs after newfs'ing the >> > filesystems. >> > >> > I'm using a 21GB array, with auto-defaults for the filesystems, so >> > /usr >> > is over 20GB in size. If I delete /usr and replace it with a 500MB >> > filesystem, leaving the remaining space unallocated, sysinstall has no >> > problem completing the newfs step. >> > >> > Anyone else had problems with sysinstall on a mid-sized array like >> > this? >> >> Yup. Me :-) >> But not on 3.0-current. I noticed that 2.2 does not like huge >> partitions, >> but this is not consnstent. > > 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. [ I am dropping the cross-post to SCSI as it is not a SCSI issue ] I agree, but I do virtually most of my new installs on 3.0 and with filesystems of 4GB or smaller. Some 16GB filesystems seem to work fine. It may very well be that the problem is in the fact that the swap device may or may not be activated at the time of newfs. Does anyone know the answer to this question? Simon --- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message