Date: 15-04-02 17:23
I've been futzing with ccd for the last four days and I've finally gotten it working correctly. Part of the problem was an error in this document (and the corresponding section of the handbook):
The author states that the e: partition may be an exact copy of the line that sets up the c: partition. Then it would turn out to be:
e: 60074784 0 unused 0 0 0 # (Cyl. 0 - 59597)
But in reality, the "unused" filesystem type for the e: partition will cause ccdconfig to barf with the error:
ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format
and this is a FAQ:
which, to sum up, states that the line above would rightfully look like this:
e: 60074784 0 4.2BSD 0 0 0 # (Cyl. 0 - 59597)
And when config'ing the ccd you'll need to use the 4.2BSD partition entries you've created instead of the c parts described in the article:
ccdconfig ccd0 64 0 /dev/da1e /dev/da2e
I should point out that you *can* do this by changing the fstype of the c partition from "unused" to "4.2BSD" instead of creating a new partition and setting the fstype of that, but you'll get scary errors from disklabel and who knows what other kind of trouble (if any) in the future.
This was my experience, and now I have a working ccd :) The key difference I can see from the article is that I was using SCSI drives, perhaps that explains the async experience.