We didn't go as far as modifying the structure definition, just the
few "bcount" variables in the ccd.c code.
The problem was that we were seeing bcount go "negative". I believe that
"newfs" of the ccd would panic the kernel, reliably. Even on "smaller"
ccds (1 Gbyte), I believe.
I'm talking about ccds configured as in:
ccdconfig -c ccd0 0 0 /dev/da0s1c
I know, this is fairly worthless as it stands, but it is done so we can
later "upgrade" the ccd to a mirror.
RSN, we will be moving to vinum. Hi Greg!
Linux, BTW, does s/w RAID5. But, it seems you can't operate in degraded
mode, and the RAID5 reconstruction happens at boot time. We've got a 130
GB RAID5 volume under Linux that takes about 10 hours to "ckraid". I hope
that this box never panics!
On Wed, 18 Aug 1999, Sheldon Hearn wrote:
> On Wed, 18 Aug 1999 09:19:20 -0400, "Mark J. Taylor" wrote:
> > There is a long as a parameter to ccdbuffer that needs to be a u_long.
> > Otherwise, you'll get panics (can't remember where).
> > Basically, bcount needs to be a u_long in all cases.
> Que? Are you sure? That means you want to change struct buf, where
> b_bcount is declared as long, as well?
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message