From: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
To: Tejun Heo <tj@kernel.org>
Cc: axboe@fb.com, jack@suse.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>, "Theodore Ts'o" <tytso@mit.edu>
Subject: Re: BUG: Unable to handle kernel paging request for data at address __percpu_counter_add
Date: Mon, 30 Nov 2015 12:48:32 +0530 [thread overview]
Message-ID: <565BF848.7060501@linux.vnet.ibm.com> (raw)
In-Reply-To: <20151123211322.GD19072@mtj.duckdns.org>
On 11/24/2015 02:43 AM, Tejun Heo wrote:
> Hello,
>
> On Thu, Nov 19, 2015 at 03:54:35PM +0530, Raghavendra K T wrote:
>> While I was creating thousands of docker container on a power8 baremetal
>> (config: 4.3.0 kernel 1TB RAM, 20core (=160 cpu) system. After creating
>> around 5600 container
>> I have hit below problem.
>> [This is looking similar to
>> https://bugzilla.kernel.org/show_bug.cgi?id=101011, but
>> kernel had Revert "ext4: remove block_device_ejected" (bdfe0cbd746aa9) since
>> it is 4.3.0 tagged kernel]
>>
>> Any hints on how to go about the fix. Please let me know if you think any
>> more information needed.
>>
>> docker daemon is device mapper based. (and it took a day to recreate the
>> problem)
>>
>> [ by disabling CONFIG_BLK_CGROUP and CONFIG_CGROUP_WRITEBACK I am able to
>> create 10k containers without any problem]
>
> Could be the same problem that Ilya is trying to fix. ie. blkdev i_wb
> pointing to a stale wb. Can you please see whether the following
> patch resolves the issue?
>
> http://lkml.kernel.org/g/1448054554-24138-1-git-send-email-idryomov@gmail.com
>
Hi Tejun,
Thanks again for the pointer. I was now able to create more than 10k
containers without any problem with CGROUP_WRITEBACK on whereas
earlier I had hit this problem few times around 5k+ containers itself.
(Also Replying to Ilya's thread).
prev parent reply other threads:[~2015-11-30 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 10:24 Raghavendra K T
2015-11-23 21:13 ` Tejun Heo
2015-11-24 6:05 ` Raghavendra K T
2015-11-30 7:18 ` Raghavendra K T [this message]
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=565BF848.7060501@linux.vnet.ibm.com \
--to=raghavendra.kt@linux.vnet.ibm.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=jack@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=tytso@mit.edu \
/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
Powered by JetHome