linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Malte Schumacher <s.schumacher@netcologne.de>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Crash when unraring large archives on btrfs-filesystem
Date: Thu, 8 Feb 2018 12:37:08 +0100	[thread overview]
Message-ID: <CAA3ktqnAt00TXGsSNpp7TyX++eZTiCO+31nY5xd8h2Zro_xktg@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtQT7pDTrOrSMF-LXrB45yP32qytTOmAqjTv6EA5nnZfmw@mail.gmail.com>

> How much RAM on the machine and how much swap available? This looks like a
> lot of dirty data has accumulated, and then also there's swapping happening.
> Both swap out and swap in.

The machine has 16GB Ram and 40GB Swap on a SSD. Its not doing much
besides being my personal file archive, so there should be plenty of
free memory for btrfs. I have remounted the filesystem with the
clear_cache option and now will apply the tweaks mentioned by Duncan.
If this does not fix the problem I will install a more current kernel
from stretch-backports. Testing currently has btrfs-progs 4.13.3-1. Is
this version safe to use and should I upgrade it along with the
kernel?

      parent reply	other threads:[~2018-02-08 11:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-07 19:57 Crash when unraring large archives on btrfs-filesystem Stefan Malte Schumacher
2018-02-08  2:59 ` Chris Murphy
2018-02-08  3:08   ` Chris Murphy
2018-02-08  7:54 ` Nikolay Borisov
     [not found] ` <CAJCQCtQT7pDTrOrSMF-LXrB45yP32qytTOmAqjTv6EA5nnZfmw@mail.gmail.com>
2018-02-08 11:37   ` Stefan Malte Schumacher [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=CAA3ktqnAt00TXGsSNpp7TyX++eZTiCO+31nY5xd8h2Zro_xktg@mail.gmail.com \
    --to=s.schumacher@netcologne.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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;
as well as URLs for NNTP newsgroup(s).