From owner-freebsd-stable Fri May 22 16:36:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15918 for freebsd-stable-outgoing; Fri, 22 May 1998 16:36:58 -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 QAA15849 for ; Fri, 22 May 1998 16:36:44 -0700 (PDT) (envelope-from shimon@sendero.simon-shapiro.org) Received: (qmail 4465 invoked by uid 1000); 23 May 1998 00:37:47 -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:37:47 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Charles Owens Subject: RE: DPT install problem Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, Tom Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On 22-May-98 Charles Owens 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. >> >> Simon > > This has me a bit nervous. This July I will be implementing an NFS > server > with a 60GB DTP-based array. My plan has been to use 2.2-stable... but > perhaps 3.0-current is my only choice? Is this -stable problem > understood, with a fix coming any time soon? Relax. It is not so bad. Here is what you do: a. Install your core system, avoiding any single file system (slice) larger than about 4GB. b. Boot the system and use disklabel -e, etc. to create the really large filesystems. c. Modify /etc/rc as per my previous post. d. Call me if there are any more problems. > Any other concerns that I should be sweating about as I'm planning on > building an array of this size? (and it will probably double in size the > following summer) Yes. Fsck on such a filesystem is a bit slower. Not too many people actually tested the filesystem code, overflowing 32bit addresses. Backup of such a partition may be interesting too. > > Thanks, > --- > ------------------------------------------------------------------------- > Charles N. Owens Email: owensc@enc.edu > http://www.enc.edu/~owensc > Network & Systems Administrator > Information Technology Services "Outside of a dog, a book is a man's > Eastern Nazarene College best friend. Inside of a dog it's > too dark to read." - Groucho Marx > ------------------------------------------------------------------------- > --- 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