From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: "cheater00 ." <cheater00@gmail.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Bad fs performance, IO freezes
Date: Tue, 27 Oct 2015 16:01:59 +0100 [thread overview]
Message-ID: <562F91E7.5030407@googlemail.com> (raw)
In-Reply-To: <CA+9GZUhtS9Y-711VSaS1-ie92x9FtZFHw5WZ5__+YgbGneU9kA@mail.gmail.com>
On 10/27/15 15:43, cheater00 . wrote:
> I have remounted without autodefrag and the issue keeps on happening.
At the risk of stating the obvious, the simplest thing is to stop using
COW with compression for torrents. It's fundamentally not useful to have
many small in-place writes, irregular compression and not encounter insane
levels of fragmentation, which - at least in the current state of btrfs -
is known to cause long stalls. Some fixes for that will be in 4.4.
Until then just do yourself a favor, stop doing the wrong thing and put
torrent downloads into a directory where they won't get COWed.
See the wiki at:
https://btrfs.wiki.kernel.org/index.php/FAQ#Can_copy-on-write_be_turned_off_for_data_blocks.3F
for more.
-h
next prev parent reply other threads:[~2015-10-27 15:02 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 12:16 Bad fs performance, IO freezes cheater00 .
2015-10-26 13:32 ` Donald Pearson
2015-10-26 13:36 ` cheater00 .
2015-10-26 13:45 ` Donald Pearson
2015-10-26 13:46 ` cheater00 .
2015-10-26 13:56 ` cheater00 .
2015-10-26 14:00 ` Donald Pearson
2015-10-26 14:25 ` Liu Bo
2015-10-26 14:38 ` cheater00 .
2015-10-26 15:40 ` cheater00 .
2015-10-26 17:43 ` cheater00 .
2015-10-26 18:31 ` cheater00 .
2015-10-27 2:00 ` cheater00 .
2015-10-27 6:39 ` Duncan
2015-10-27 8:55 ` cheater00 .
2015-10-27 11:44 ` Austin S Hemmelgarn
2015-10-27 13:00 ` Henk Slager
2015-10-27 13:30 ` Austin S Hemmelgarn
2015-10-27 14:22 ` cheater00 .
2015-10-27 14:26 ` cheater00 .
2015-10-27 14:30 ` cheater00 .
2015-10-27 14:43 ` cheater00 .
2015-10-27 15:01 ` Holger Hoffstätte [this message]
2015-10-27 15:05 ` cheater00 .
2015-10-27 15:07 ` cheater00 .
2015-10-27 15:22 ` Holger Hoffstätte
2015-10-27 15:26 ` Austin S Hemmelgarn
2015-10-29 13:03 ` cheater00 .
2015-10-29 14:00 ` Austin S Hemmelgarn
2015-10-29 15:49 ` cheater00 .
2015-10-29 18:49 ` Henk Slager
2015-10-29 20:01 ` Austin S Hemmelgarn
2015-11-06 13:37 ` cheater00 .
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=562F91E7.5030407@googlemail.com \
--to=holger.hoffstaette@googlemail.com \
--cc=cheater00@gmail.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).