Re: ufs related panic with latest current

2003-09-11 Thread Dag-Erling Smørgrav
Tomi Vainio - Sun Finland [EMAIL PROTECTED] writes: If you could just give instructions what you wanna get when system panics I might be able to persuade the other that we should crash our system once more. I already have. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED]

Re: ufs related panic with latest current

2003-09-10 Thread Doug White
On Tue, 9 Sep 2003, Tomi Vainio - Sun Finland wrote: Tomi Vainio - Sun Finland writes: Our system died when using iozone -a to ~300G vinum partition made from four disks. Sources were cvsupped 7.9.2003. Second panic an hour later. Any good ideas how to fix this? Tomppa panic:

Re: ufs related panic with latest current

2003-09-10 Thread Tomi Vainio - Sun Finland
Doug White writes: On Tue, 9 Sep 2003, Tomi Vainio - Sun Finland wrote: Tomi Vainio - Sun Finland writes: Our system died when using iozone -a to ~300G vinum partition made from four disks. Sources were cvsupped 7.9.2003. Second panic an hour later. Any good ideas how

Re: ufs related panic with latest current

2003-09-10 Thread Dag-Erling Smørgrav
Tomi Vainio - Sun Finland [EMAIL PROTECTED] writes: First maxusers was 0 then when changed it to 8. That's a regression. Keep it at 0. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list

Re: ufs related panic with latest current

2003-09-10 Thread Tomi Vainio - Sun Finland
Dag-Erling Smørgrav writes: Tomi Vainio - Sun Finland [EMAIL PROTECTED] writes: First maxusers was 0 then when changed it to 8. That's a regression. Keep it at 0. I understood that there is a bug on new kmem allocator and this was an attempt to reduce kmem allocations but it didn't

Re: ufs related panic with latest current

2003-09-10 Thread Dag-Erling Smørgrav
Tomi Vainio - Sun Finland [EMAIL PROTECTED] writes: Dag-Erling Smørgrav writes: Tomi Vainio - Sun Finland [EMAIL PROTECTED] writes: First maxusers was 0 then when changed it to 8. That's a regression. Keep it at 0. I understood that there is a bug on new kmem allocator and this was an

Re: ufs related panic with latest current

2003-09-10 Thread Tomi Vainio - Sun Finland
Dag-Erling Smørgrav writes: The backtrace you showed seems to indicate that the panic happened somewhere in the softupdates code, but IIRC that code has a fairly conservative built-in limit on memory consumption and degrades gracefully when it hits that limit. It's likely that

Re: ufs related panic with latest current

2003-09-10 Thread Dag-Erling Smørgrav
Tomi Vainio - Sun Finland [EMAIL PROTECTED] writes: Second trace didn't have anything to do with fs only fork system calls there so your expanation sounds reasonable. We probably don't see this problem again because system now has enough memory (256M). It would be really useful to know where

Re: ufs related panic with latest current

2003-09-10 Thread Tomi Vainio - Sun Finland
Dag-Erling Smørgrav writes: It would be really useful to know where the fault lies. We might even (God forbid!) figure out a way to fix it. You can easily force the system to boot with less than the full amount of memory by setting hw.physmem to e.g. 64m in /boot/loader.conf or at the

ufs related panic with latest current

2003-09-09 Thread Tomi Vainio - Sun Finland
Our system died when using iozone -a to ~300G vinum partition made from four disks. Sources were cvsupped 7.9.2003. Tomppa kmem_malloc(8192): kmem_map too small: 28229632 total allocated db trace Debugger(c03cc728,c0429ce0,c03db0bd,ca6c4800,100) at Debugger+0x54

ufs related panic with latest current

2003-09-09 Thread Tomi Vainio - Sun Finland
Tomi Vainio - Sun Finland writes: Our system died when using iozone -a to ~300G vinum partition made from four disks. Sources were cvsupped 7.9.2003. Second panic an hour later. Any good ideas how to fix this? Tomppa panic: kmem_malloc(4096): kmem_map too small: 28229632 total