From owner-freebsd-hackers Sat Sep 13 21:44:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA21118 for hackers-outgoing; Sat, 13 Sep 1997 21:44:35 -0700 (PDT) Received: from pobox.com (ras123.microplus.ca [207.81.20.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA21106 for ; Sat, 13 Sep 1997 21:44:28 -0700 (PDT) Received: (from brianc@localhost) by pobox.com (8.8.5/8.8.5) id AAA05759; Sun, 14 Sep 1997 00:43:17 -0400 (EDT) Message-ID: <19970914004317.33168@pobox.com> Date: Sun, 14 Sep 1997 00:43:17 -0400 From: Brian Campbell To: freebsd-hackers@FreeBSD.ORG Subject: Re: ccd / newfs error References: <19970912232911.50519@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: ; from Chris Timmons on Sat, Sep 13, 1997 at 10:57:01AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > 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. On Sat, Sep 13, 1997 Chris Timmons wrote: > 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? I retried it explicitly specifying /dev/rccd0a, same error.