On Wed, 7 Aug 2013 00:42:27 +0800
Tomasz Chmielewski man...@wpkg.org wrote:
What do I have to do to reproduce it here? How do you generate the
load? What is the disk setup, what the qgroups setup?
Unfortunately I don't have a way to reproduce, as the issue
happened to me only once.
I
I'm pretty I encountered the same leak over here, 15 days uptime and I
had consistent out of memory problems, I got angry and did go in
single user mode and noticed that with only systemd-screen-bash(2) I
had 2 GB of memory used on 4 GB total. This box mostly has random
reads and just before the
On Tue, 06 Aug 2013 07:24:26 +0200
Arne Jansen sensi...@gmx.net wrote:
On 05.08.2013 18:35, Tomasz Chmielewski wrote:
I am trying to use qgroups
functionality with a basic random-write workload, it constantly
keeps leaking memory within few minutes of IO, there is either
out-of-memory
I am trying to use qgroups
functionality with a basic random-write workload, it constantly
keeps leaking memory within few minutes of IO, there is either
out-of-memory killer trying to kill some tasks or there are
page-allocation failures that btrfs or other kernel module
experiences.
Hello.
I am trying to use qgroups
functionality with a basic random-write workload, it constantly
keeps leaking memory within few minutes of IO, there is either
out-of-memory killer trying to kill some tasks or there are
page-allocation failures that btrfs or other kernel module
On Tue, 6 Aug 2013 07:29:03 +0800
Wang Shilong wangshilong1...@gmail.com wrote:
Hello.
I am trying to use qgroups
functionality with a basic random-write workload, it constantly
keeps leaking memory within few minutes of IO, there is either
out-of-memory killer trying to kill some
On 05.08.2013 18:35, Tomasz Chmielewski wrote:
I am trying to use qgroups
functionality with a basic random-write workload, it constantly
keeps leaking memory within few minutes of IO, there is either
out-of-memory killer trying to kill some tasks or there are
page-allocation failures that
Hi Arne, I will start with 3.6 then try to bisect it as you suggest.
However I am currently tied with some high priority work, will get to
this after it.
--Shyam
On Wed, Feb 27, 2013 at 1:12 PM, Arne Jansen sensi...@gmx.net wrote:
On 02/15/13 05:34, shyam btrfs wrote:
Hi Arne,
Yes this
On 02/15/13 05:34, shyam btrfs wrote:
Hi Arne,
Yes this addresses the crash during mount. Thanks.
But still I have the consistent out-of-memory issue when running
random 4K writes with qgroup enabled. I will see if I can get some
steps for you to recreate the problem.
Can you please try
Hi Arne,
Yes this addresses the crash during mount. Thanks.
But still I have the consistent out-of-memory issue when running
random 4K writes with qgroup enabled. I will see if I can get some
steps for you to recreate the problem.
--Shyam
On Wed, Feb 13, 2013 at 4:52 PM, Arne Jansen
On 12.02.2013 08:25, shyam btrfs wrote:
Hi Arne, Jan,
I am using btrfs directly from Linux 3.8rc5 (commit
949db153b6466c6f7cad5a427ecea94985927311). I am trying to use qgroups
functionality with a basic random-write workload, it constantly
keeps leaking memory within few minutes of IO,
On 12.02.2013 08:31, shyam btrfs wrote:
Also immediately after this problem, its impossible to mount the
filesystem. it consistently fails with
no luck here either. I tried a sync-heavy workload and crashed it
in the middle. mount took a while but succeeded.
Maybe your debug tree contains
Hi Arne,
I realize my first mail that had logs as attachment didnt show up. I
uploaded the logs at
https://docs.google.com/file/d/0B1JpdTsfQ1vgVTkwRHJjcHplZlk/edit?usp=sharing
This has the debug-tree when btrfs cannot mount (i.e. after the
crash). Also there are meminfo/slabinfo that I kept
On 12.02.2013 08:31, shyam btrfs wrote:
Also immediately after this problem, its impossible to mount the
filesystem. it consistently fails with
[ 2092.254428] BUG: unable to handle kernel NULL pointer dereference
at 03c4
[ 2092.255945] IP: [a033d0be]
Hi Shyam,
I sent a patch to the list
[PATCH] Btrfs: fix crash in log replay with qgroups enabled
that hopefully addresses this problem. As I haven't been able to
reproduce it, I also haven't been able to test it.
Could be please see if it fixes your problem and makes the filesystem
mountable
Also immediately after this problem, its impossible to mount the
filesystem. it consistently fails with
[ 2092.254428] BUG: unable to handle kernel NULL pointer dereference
at 03c4
[ 2092.255945] IP: [a033d0be]
btrfs_search_old_slot+0x63e/0x940 [btrfs]
[ 2092.257340] PGD
16 matches
Mail list logo
