From: Tomasz Chmielewski <tch@virtall.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
jgoerzen@complete.org
Subject: Re: Lots of trouble hanging when rm files with many extents
Date: Sun, 20 Oct 2013 23:51:18 +0900 [thread overview]
Message-ID: <20131020235118.3a918ba3@virtall.com> (raw)
> but I am not sure if that was the right thing to do. This is
> producing OOM issues and leading to system crashes (including
> eventual panics) with such alarming frequency that I wonder if
> perhaps there is something different about my setup than others.
FYI, I'm seeing similar / random hangs on systems with btrfs,
compress-force=zlib, qgroups enabled. The systems have 32 GB RAM.
Sometimes, I can review old logs (after force reboot) and see OOM,
allocation failures and such.
The scenario there are snapshots, rsync with --inplace flag, which can
fragment files a lot.
I'll do some more tests with lots of extents to see if it's
reproducible here as well.
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2013-10-20 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-20 14:51 Tomasz Chmielewski [this message]
2013-10-21 3:40 ` Lots of trouble hanging when rm files with many extents John Goerzen
2013-10-25 13:41 ` rm with quotas can cause panic (was Re: Lots of trouble hanging when rm files with many extents) John Goerzen
-- strict thread matches above, loose matches on Subject: below --
2013-10-22 9:40 Lots of trouble hanging when rm files with many extents Tomasz Chmielewski
2013-10-21 4:36 Tomasz Chmielewski
2013-10-21 9:58 ` Duncan
2013-10-21 13:47 ` John Goerzen
2013-10-19 23:12 John Goerzen
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=20131020235118.3a918ba3@virtall.com \
--to=tch@virtall.com \
--cc=jgoerzen@complete.org \
--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).