From owner-freebsd-hackers Sat Sep 13 10:57:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA16642 for hackers-outgoing; Sat, 13 Sep 1997 10:57:10 -0700 (PDT) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA16634 for ; Sat, 13 Sep 1997 10:57:07 -0700 (PDT) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by pahtoh.cwu.edu (8.8.7/8.8.7) with ESMTP id KAA18882; Sat, 13 Sep 1997 10:57:02 -0700 (PDT) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.7/8.8.7) with SMTP id KAA27918; Sat, 13 Sep 1997 10:57:01 -0700 (PDT) Date: Sat, 13 Sep 1997 10:57:01 -0700 (PDT) From: Chris Timmons To: Brian Campbell cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ccd / newfs error In-Reply-To: <19970912232911.50519@pobox.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Over the months there has been some correspondence about newfs and its behavior when presented with the block special rather than the raw special. You'll need to search the archives in -current and -hackers for newfs. IIRC Justin Gibbs and Nate Williams may have been involved in the discussion. Normally I just newfs the raw special file - e.g 'newfs /dev/rccd0c' and have had no trouble. Can you try that and see if your problems go away? -Chris On Fri, 12 Sep 1997, Brian Campbell wrote: > Has anyone else had problems newfs'ing ccd filesystems? It works > for some interleaves but not others. The newfs error message is > less than informative. > > Is there a guideline for getting the best performance out of a > filesytems (newfs/tunefs options) for reads vs writes, large vs > small files, etc?