From: "Andrew E. Mileski" <andrewm@isoar.ca>
To: linux-btrfs@vger.kernel.org
Subject: Re: Is btrfs related to OOM death problems on my 8GB server with both 3.15.1 and 3.14?
Date: Sat, 05 Jul 2014 11:17:15 -0400 [thread overview]
Message-ID: <53B816FB.7080909@isoar.ca> (raw)
In-Reply-To: <20140705144318.GT26932@merlins.org>
On 2014-07-05 10:43 AM, Marc MERLIN wrote:
> On Sat, Jul 05, 2014 at 09:47:09AM -0400, Andrew E. Mileski wrote:
>> On 2014-07-03 9:19 PM, Marc MERLIN wrote:
>>> I upgraded my server from 3.14 to 3.15.1 last week, and since then it's been
>>> running out of memory and deadlocking (panic= doesn't even work).
>>> I downgraded back to 3.14, but I already had the problem once since then.
>>
>> I didn't see any mention of the btrfs utility version in this thread
>> (I may be blind though).
>>
>> My server was suffering from frequent panics upon scrub / defrag /
>> balance, until I updated the btrfs utility. That resolved all my
>> issues.
>
> Really? The userland tool should only send ioctls to the kernel, I
> really can't see how it would cause the kernel code to panic or not.
>
> gargamel:~# btrfs --version
> Btrfs v3.14.1
> which is the latest in debian unstable.
It reached the point that I got so frustrated that I built the
utilities from git, as an up-to-date package wasn't available at the
time. I'm currently using v3.14.2 but v3.14.1 was the version that
resolved my server's panics.
I've not looked into the code very deeply yet, so I can't theorize on
why it resolved my server's panics. I can only state with complete
certainty that it did. I too was somewhat surprised.
However, it seems we've probably now ruled it out in your case.
~~
Andrew E. Mileski
next prev parent reply other threads:[~2014-07-05 15:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 1:19 Is btrfs related to OOM death problems on my 8GB server with both 3.15.1 and 3.14? Marc MERLIN
2014-07-04 4:33 ` Russell Coker
2014-07-04 6:04 ` Marc MERLIN
2014-07-04 6:23 ` Satoru Takeuchi
2014-07-04 14:24 ` Marc MERLIN
2014-07-04 14:45 ` Russell Coker
2014-07-04 15:07 ` Marc MERLIN
2014-07-04 22:13 ` Duncan
2014-07-05 13:47 ` Andrew E. Mileski
2014-07-05 14:43 ` Marc MERLIN
2014-07-05 15:17 ` Andrew E. Mileski [this message]
2014-07-06 14:58 ` Marc MERLIN
2014-07-13 14:29 ` btrfs is " Marc MERLIN
2014-07-13 15:37 ` Marc MERLIN
2014-07-13 15:45 ` btrfs quotas " Marc MERLIN
2014-07-14 1:36 ` Qu Wenruo
2014-07-14 2:43 ` Marc MERLIN
2014-07-14 1:24 ` btrfs is " Qu Wenruo
2014-07-16 0:36 ` Jérôme Poulin
2014-07-16 15:55 ` Marc MERLIN
2014-07-17 2:22 ` Marc MERLIN
2014-07-16 0:45 ` Is btrfs " Jérôme Poulin
2014-07-05 14:27 ` Andrew E. Mileski
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=53B816FB.7080909@isoar.ca \
--to=andrewm@isoar.ca \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).