From owner-freebsd-hackers Mon May 12 16:53:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA13942 for hackers-outgoing; Mon, 12 May 1997 16:53:42 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id QAA13937 for ; Mon, 12 May 1997 16:53:39 -0700 (PDT) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA06009; Mon, 12 May 1997 16:53:45 -0700 Date: Mon, 12 May 1997 16:53:45 -0700 (PDT) From: "Brian N. Handy" To: hackers@freebsd.org Subject: newfs hangs my system? Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I just got a couple of new drives for my machine, and I've been trying to format the drives...to no avail. (2.2-STABLE) Well, that's not completely true. I was finally able to talk sysinstall into doing the brunt of the work for me. I've got two 4GB drives, and I thought it would be real cool to put 80MB of swap on the front of each drive and then CCD the balance of the two drives together. However, I have something wrong. Newfs is hanging my machine. I've been able to disklabel my CCD, here it is: lambic:~ [11]->disklabel ccd0 [...] 3 partitions: # size offset fstype [fsize bsize bps/cpg] c: 16701056 0 4.2BSD 0 0 0 # (Cyl. 0 -8154*) ...but when I try to newfs it, the system hangs. I'll do something like: lambic:~ [12]->newfs -b 8192 -f 1024 /dev/ccd0c /a --> and it'll run for a few seconds, creating things like crazy, get to about the second line and hang the whole system. Locks everything up tight. This is not unique to my ccd filesystem either; if I just try to newfs the drives alone (/dev/sd1s1e for example) I get the same behavior. sysinstall doesn't seem to have this problem, which suggests sysinstall knows something I don't. What am I doing wrong? What do I need to do to mount my CCD? Halp! Thanks, Brian