Re: ccd bugs (was: Kernel hacker tasks seek interested hackers)

1999-08-18 Thread Mark J. Taylor
This may be related: 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. I haven't gotten around, because of the NetMAX for Linux project, to comitting things like this

Re: ccd bugs (was: Kernel hacker tasks seek interested hackers)

1999-08-18 Thread Sheldon Hearn
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

Re: ccd bugs (was: Kernel hacker tasks seek interested hackers)

1999-08-18 Thread Matthew Dillon
: : 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? :

Re: ccd bugs (was: Kernel hacker tasks seek interested hackers)

1999-08-18 Thread Andrew Gallatin
Matthew Dillon writes: This is very odd. I use several multi-disk ccd stripes, including one at BEST across three 18G drives (one 54G partition!). I've never had a problem. I believe that at some point in the past 'newfs' and 'fsck' had overflow problems, but

Re: ccd bugs (was: Kernel hacker tasks seek interested hackers)

1999-08-18 Thread Greg Lehey
On Wednesday, 18 August 1999 at 9:50:54 -0400, Mark J. Taylor wrote: 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