From: Roger Binns <rogerb@rogerbinns.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: disable snapshot aware defrag for now
Date: Mon, 03 Feb 2014 19:19:48 -0800 [thread overview]
Message-ID: <lcpm87$15e$1@ger.gmane.org> (raw)
In-Reply-To: <52EFD19C.3050404@fb.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/02/14 09:27, Josef Bacik wrote:
> It is so totally broken that I don't want it being turned on by anybody
> who can't edit this and change it themselves.
The symptoms I saw are huge amounts of kernel memory consumption, possibly
till exhaustion of swap. Are there other ways in which is it broken (eg
corruption)?
Also is this patch making its way to the various stables?
Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
iEYEARECAAYFAlLwXE8ACgkQmOOfHg372QRLngCgpc445lPvM7YhGUxVdlU2O4vN
1CUAoM2NmeGPOeYxOji4yL4VRysBnTxg
=sQ3M
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-02-04 3:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 21:05 [PATCH] Btrfs: disable snapshot aware defrag for now Josef Bacik
2014-02-03 14:48 ` David Sterba
2014-02-03 17:27 ` Josef Bacik
2014-02-04 3:19 ` Roger Binns [this message]
2014-02-04 14:07 ` Josef Bacik
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='lcpm87$15e$1@ger.gmane.org' \
--to=rogerb@rogerbinns.com \
--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).