From owner-freebsd-fs  Wed Feb  4 07:58:31 1998
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA07538
          for freebsd-fs-outgoing; Wed, 4 Feb 1998 07:58:31 -0800 (PST)
          (envelope-from owner-freebsd-fs@FreeBSD.ORG)
Received: from silvia.HIP.Berkeley.EDU (ala-ca36-04.ix.netcom.com [207.93.42.196])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07532
          for <freebsd-fs@freebsd.org>; Wed, 4 Feb 1998 07:58:26 -0800 (PST)
          (envelope-from asami@vader.cs.berkeley.edu)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.8/8.6.9) id HAA04258; Wed, 4 Feb 1998 07:58:11 -0800 (PST)
Date: Wed, 4 Feb 1998 07:58:11 -0800 (PST)
Message-Id: <199802041558.HAA04258@silvia.HIP.Berkeley.EDU>
To: cdillon@inter-linc.net
CC: freebsd-fs@FreeBSD.ORG
In-reply-to: <XFMail.980204093810.cdillon@inter-linc.net> (message from Chris Dillon on Wed, 04 Feb 1998 09:17:45 -0600 (CST))
Subject: Re: May have pounced on something weird with ccd and newfs  (rat
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-fs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-fs"


 * > * I=128     newfs -b 8192 -f 1024 fails with "write error: 2047871
 * > *                                             wtfs: invalid argument".

 * I'm not quite sure what you mean by "old" disklabel, but I started out fresh
 * with these drives, and labeled them symmetrically with using ccd's in mind..

What I meant is if you edit the disklabel on a ccd at a certain
interleave, the label will "stick" when you later reconfigure the ccd
with a different interleave (since the disklabel exists in the first
sector of the first partition).

Since the interleaves are increasing in your test order, it's possible
that the last few blocks that the disklabel says exist may not exist.

 * Here's the labels for sd0, sd1, and ccd0, and the output of ccdconfig -g.

You are missing the output of ccdconfig -g.  I can't diagnose the
problem without it.

 * root@cheetah [/root] # disklabel ccd0

 * sectors/unit: 2047872

See the number above (the error from wtfs).  It is second from the
last block, which could be invalid at a 128 interleave.

 * 3 partitions:
 * #        size   offset    fstype   [fsize bsize bps/cpg]
 *   a:  1023936        0    4.2BSD     1024  8192     0   # (Cyl.    0 - 499*)
 *   b:  1023936  1023936    4.2BSD     1024  8192     0   # (Cyl.  499*- 999*)
 *   c:  2047872        0    unused        0     0         # (Cyl.    0 - 999*)

So you do have a disklabel.  (The ccd driver will return a "default"
label with only partition "c" and type "4.2BSD" if you don't write one
yourself...that is often good enough, there usually is no point in
sub-partitioning the ccd if you're combining disks is the first
place. :)

Satoshi