From: Badari Pulavarty <pbadari@gmail.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: melgor@ie.ibm.com, linux-mm <linux-mm@kvack.org>
Subject: Re: migrate_pages() failure
Date: Fri, 26 Oct 2007 16:07:47 -0700 [thread overview]
Message-ID: <1193440067.19950.7.camel@dyn9047017100.beaverton.ibm.com> (raw)
In-Reply-To: <1193432242.19950.1.camel@dyn9047017100.beaverton.ibm.com>
On Fri, 2007-10-26 at 13:57 -0700, Badari Pulavarty wrote:
> Hi,
>
> While playing with hotplug memory remove on x86-64 and ppc64, I noticed
> that some of the memory sections can not be offlined. What I noticed is
> migrate_pages() fails to move the pages. I added debug and page_owner
> to track these pages. I am wondering why they couldn't be migrated ?
> Ideas ?
>
> BTW, I did echo 3 > /proc/sys/vm/drop_caches to drop all the
> caches before trying to offline (on this cleanly rebooted machine).
>
> nr_failed 0 retry 116
> migrate pages failed 3f025/3/3f00000000800
> migrate pages failed 3f048/3/3f00000000800
> migrate pages failed 3f04c/3/3f00000000800
> migrate pages failed 3f06e/3/3f00000000800
> migrate pages failed 3f092/3/3f00000000800
> migrate pages failed 3f093/3/3f00000000800
> migrate pages failed 3f097/3/3f00000000800
> migrate pages failed 3f0b2/3/3f00000000800
> migrate pages failed 3f0b7/3/3f00000000800
> migrate pages failed 3f0b8/3/3f00000000800
> migrate pages failed 3f100/3/3f00000000800
> migrate pages failed 3f196/3/3f00000000800
> migrate pages failed 3f19d/3/3f00000000800
> migrate pages failed 3f1b7/3/3f00000000800
> migrate pages failed 3f1ba/3/3f00000000800
> migrate pages failed 3f1c8/3/3f00000000800
>
Digged up little more ..
All these pages are "reiserfs" backed file and reiserfs doesn't
have migratepage() handler. reiserfs_releasepage() gives up
since one of the buffer_head attached to the page is dirty or locked :(
Nothing much migrate pages could do :(
Thanks,
Badari
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-10-26 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 20:57 Badari Pulavarty
2007-10-26 23:07 ` Badari Pulavarty [this message]
2007-10-26 23:51 ` KAMEZAWA Hiroyuki
2007-10-29 20:44 ` Christoph Lameter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1193440067.19950.7.camel@dyn9047017100.beaverton.ibm.com \
--to=pbadari@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=melgor@ie.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox