Sorry, I was just looking at the other problem to hard to notice the
obvious!
# newfs ccd0c, not /dev/ccd0c.
On Wed, 17 Jan 2007, Chris Mika wrote:
Although I did get an error: # newfs /dev/ccd0c
newfs: /dev/ccd0c: not a character-special device, but it still ran. Any
suggestions anyone? Can this be ignored (I'm guessing since it printed it it
can't be)?
On Wed, 17 Jan 2007, Chris Mika wrote:
I sat down and calculated one cylinder, and it's not 63 sectors, it's 1008.
So I redid the disklabel and it seems to be working. I ran newfs and it's
reporting 600GB.
You can't create a partition on ccd0, you must use ccd0c.
On Wed, 17 Jan 2007, Chris Mika wrote:
I've read that. That's why I began the offset using disklabel's default
setting, which is 63. Sorry, that's why I said you can ask for
clarification.
As for the second part, it wasn't so clear, but with FreeBSD's ccd you
create the file system on /dev/ccd0c so I assumed it was the same. If you
use disklabel -E ccd0 it can't get the approrpriate geometry.
On Wed, 17 Jan 2007, christian widmer wrote:
first:
YOU WROTE: "-> creating one partition of type ccd spanning entire disk"
i take you're word.... then you should have a close look at 'man ccd'
"Note that the `raw' partitions of the disks should not be combined. Each
component partition should be offset at least one cylinder from the
beginning
of the component disk."
this is not what you said you did.
second:
i would use disklabel to create explicitly a partition on ccd0 (not
using 'c'). but i'm not sure if this is really necessary.
On Wednesday 17 January 2007 19:11, Chris Mika wrote:
I'm trying to get CCD working correctly, but it just doesn't want to.
I have two identical 300GB disks that I'm trying to interleave.
Here's exactly what I'm doing:
# fdisk -i wd1
# fdisk -i wd3
# disklabel -E wd1
-> creating one partition of type ccd spaning entire disk
# disklabel -E wd3
-> creating one partition of type ccd spaning entire disk
# ccdconfig ccd0 32 0 /dev/wd1a /dev/wd3a
# newfs /dev/ccd0c
When I run newfs it only creates a 300GB filesystem, whereas it SHOULD
create a 600GB file system.
Any ideas? I can send the dmesg or any output if that helps (I didn't to
save space).
-Chris Mika
