From owner-freebsd-alpha Wed Mar 28 15: 9:58 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 2100037B72D; Wed, 28 Mar 2001 15:09:56 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id SAA15901; Wed, 28 Mar 2001 18:09:55 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2SN9PI79522; Wed, 28 Mar 2001 18:09:25 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15042.28453.158495.901316@grasshopper.cs.duke.edu> Date: Wed, 28 Mar 2001 18:09:25 -0500 (EST) To: obrien@FreeBSD.ORG Cc: alpha@FreeBSD.ORG Subject: Re: Is `ccd' broken on Alpha? In-Reply-To: <20010328000954.C18676@dragon.nuxi.com> References: <20010328000954.C18676@dragon.nuxi.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org David O'Brien writes: > I've tried this with both 4.2-RELEASE, and 5-CURRENT and get the same > result. When I newfs a ccd partition, it runs *very* quickly -- at the > speed of ``newfs -n''. It doesn't seem to write anything to disk, as > fsck fails. Any body have any ideas? > > > # disklabel da0 |grep e: > e: 13421524 4352000 4.2BSD 1024 8192 22 # (Cyl. 270*- 1106*) > # disklabel da1 |grep e: > e: 13421524 4352000 4.2BSD 1024 8192 22 # (Cyl. 270*- 1106*) > # ccdconfig -C > # disklabel ccd0 > c: 26842880 0 unused 0 0 # (Cyl. 0 - 13106*) > e: 26842880 0 4.2BSD 0 0 0 # (Cyl. 0 - 13106*) > # newfs /dev/ccd0e > /dev/ccd0e: 26842880 sectors in 6554 cylinders of 1 tracks, 4096 sectors > 13106.9MB in 410 cyl groups (16 c/g, 32.00MB/g, 7936 i/g) > super-block backups (for fsck -b #) at: > 32, 65568, 131104, 196640, 262176, 327712, 393248, 458784, 524320, 589856, > ..snip.. > # fsck /dev/ccd0e > ** /dev/ccd0e > BAD SUPER BLOCK: MAGIC NUMBER WRONG > ..snip.. Pilot error of some type? It works fine for me using 'c' paritions. What's the magic incantation to our diskabel to get a reasonably complete set of default paritions onto a disk? Dillon was pushing something a few months ago that turned into a flame fest. Did it ever happen? Or was that for slices in fdisk? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message