[Top] [All Lists]

Re: xfsdump stuck in io_schedule

To: zlatko.calusic@xxxxxxxx
Subject: Re: xfsdump stuck in io_schedule
From: Andrew Morton <akpm@xxxxxxxxx>
Date: Fri, 15 Nov 2002 14:32:34 -0800
Cc: Andi Kleen <ak@xxxxxxx>, linux-xfs@xxxxxxxxxxx
References: <dnfzu3yw8u.fsf@magla.zg.iskon.hr> <20021115135233.A13882@oldwotan.suse.de> <dnlm3v9ebk.fsf@magla.zg.iskon.hr> <20021115140635.A31836@wotan.suse.de> <dnr8dmj1i1.fsf@magla.zg.iskon.hr>
Sender: linux-xfs-bounce@xxxxxxxxxxx
Zlatko Calusic wrote:
> Oh, yes, you're completely right, of course. It's the pinned part of
> page cache that makes big pressure on the memory. Whole lot of
> inactive page cache pages (~700MB in my case) is not really good
> indicator of recyclable memory, when (probably) a big part of it is
> pinned and can't be thrown out. So it is VM, after all.

Does xfs_dump actually pin 700 megs of memory??

If someone could provide a detailed description of what xfs_dump
is actually doing internally, that may help me shed some light.
xfs_dump is actually using kernel support for coherency reasons,
is that not so?   How does it work?

Does the machine have highmem?

What was the backtrace into the page allocation failure?

<Prev in Thread] Current Thread [Next in Thread>