Moin moin... I'm not sure where is the best list to send this, since I've seen it under both -current and -stable, so you'll have to do. Has anyone seen panics like panic: vinvalbuf: dirty bufs mp_lock = 000000000001; cpuid = 0; lapic.id = 0100000000 I get this regularly when newfs'ing a disk that I've previously newfs'ed, apparently when I've given options like -b 32768 or 65536 (which works), followed by the default value for -b. I've been trying different options to see the effect on the filesystem created. I'm also trying to get -i as large as possible since the filesystem will have no more than one file, or -i 1776something. (I get an out-of-range error but no panic if -i is too large), although my last panic was triggered by the default values for everything. I'm seeing it now with -stable cvsup'ed a few hours ago, but I saw it a few days ago with a -current from last year, so it seems to have been around for a while. If you haven't seen this and need more info, I'll be happy to pass it along. (use the reply-to header if needed since i'm not suscirbed to this list) Now I think I'll see if I can have any sort of success with the already-newfscked-up disk, and try the latest -current just for grins. thanks, barry `braneless' bouwsma, teledanmarQinterneT -- ARRGH!!@! If you are the victim of a B0RKENED MAIL SYSTEM, yo REPENT!!! PURGE THE EVIL OF REDMOND FROM YOUR HARD DRIVES!!!!1! mange tak, To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
