Re: ENOMEM @ RELENG_6 graid3

2006-06-27 Thread Pawel Jakub Dawidek
On Mon, Jun 26, 2006 at 07:34:51PM +0400, Dmitry Morozovsky wrote: > Dear colleagues, > > turning on bootverbose reveals additional info to > > ad10: FAILURE - out of memory in start > > under load this machine (5 ata disks, most of their space allocated for 2 > graid3's) many messages like >

Re: ENOMEM @ RELENG_6 graid3

2006-06-27 Thread Dmitry Morozovsky
On Tue, 27 Jun 2006, Eric Anderson wrote: EA> > As to ENOMEM/no memory in start, I'm fairly sure machine is not in generic EA> > memory-shortage; and, these errors are generated only on machine with EA> > graid3. EA> EA> What does your kernel config look like? Are you using (or did you ever use)

Re: ENOMEM @ RELENG_6 graid3

2006-06-27 Thread Eric Anderson
Dmitry Morozovsky wrote: On Mon, 26 Jun 2006, Eric Anderson wrote: EA> > turning on bootverbose reveals additional info to EA> > ad10: FAILURE - out of memory in start EA> > EA> > under load this machine (5 ata disks, most of their space allocated for 2 EA> > graid3's) many messages like EA>

Re: ENOMEM @ RELENG_6 graid3

2006-06-27 Thread Dmitry Morozovsky
On Mon, 26 Jun 2006, Eric Anderson wrote: EA> > turning on bootverbose reveals additional info to EA> > ad10: FAILURE - out of memory in start EA> > EA> > under load this machine (5 ata disks, most of their space allocated for 2 EA> > graid3's) many messages like EA> > EA> > ENOMEM 0xc6e834a4 o

Re: ENOMEM @ RELENG_6 graid3

2006-06-26 Thread Eric Anderson
Dmitry Morozovsky wrote: Dear colleagues, turning on bootverbose reveals additional info to ad10: FAILURE - out of memory in start under load this machine (5 ata disks, most of their space allocated for 2 graid3's) many messages like ENOMEM 0xc6e834a4 on 0xc493c080(ad8) ENOMEM 0xc703fdec

ENOMEM @ RELENG_6 graid3

2006-06-26 Thread Dmitry Morozovsky
Dear colleagues, turning on bootverbose reveals additional info to ad10: FAILURE - out of memory in start under load this machine (5 ata disks, most of their space allocated for 2 graid3's) many messages like ENOMEM 0xc6e834a4 on 0xc493c080(ad8) ENOMEM 0xc703fdec on 0xc4960480(ad10) ENOMEM 0x