On Thu, Jun 26, 2003 at 03:52:01PM -0400, leam wrote:
> Andrey Petrov wrote:
> >On Thu, Jun 26, 2003 at 03:36:33PM -0400, leam wrote:
> >
> >>Is there a way to cut down the kdump output? Last night I had *lots* of 
> >>"\0\0\0" lines. I'll read up on kdump and report back when I have 
> >>something.
> >>
> >
> >
> >You can exclude data transferred back and forth in syscalls by specifying
> >-t flags. Something like '-t cnis' should give you smaller trace. I'd also
> >create small filesystem for test.
> >
> >	Andrey
> 
> Hmm... on the other hand, I was just forcibly reminded of something. The 
> dump seems to work on the smaller filesystem (221M) but dies on the 
> larger one (1.3G).

If dump behaves the same way on -current and 1.6.1, I'd suspect dump first.

>			 However, I was just compiling bind and got a "virtual 
> memory exhausted" error. The machine has 128 physical and 256 swap, and 
> right now wasn't doing much beside the compile.

Usually 'unlimit' helps.

	Andrey