From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: [RFC] Add an option to disable automatic chunk reclamation.
Date: Mon, 13 Jul 2015 07:58:23 -0400 [thread overview]
Message-ID: <55A3A7DF.8080009@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
Since upgrading to a kernel with the automatic chunk reclamation
patches, I've noticed a number of issues with BTRFS that all seem to
either be caused by, or are further exacerbated by, this 'feature'.
The four big issues I've seen regarding it are:
1. TRIM/DISCARD support is broken as a (partial?) result of this.
2. It appears to expose underlying issues with the defrag code (stuff
ending up more fragmented after defrag).
3. Since upgrading to a kernel with this patch, most of the BTRFS
filesystems that I have that are very rewrite heavy have gotten very
noticeably slower that they were beforehand (and this goes away when I
run them on a kernel without auto-reclaim).
4. All of my filesystems are experiencing seemingly non-deterministic
delays around most large scale VFS level operations (eg, deleting or
relocating lots of files)
While I understand that this feature does solve (at least partially) an
very real issue with BTRFS, there were a number of people who never had
this issue to begin with because we ran regular balance operations on
our filesystems.
Based on this, I would like to propose that some method be provided to
disable auto-reclaim be added. Personally, I would prefer to leave it
as the default and have a mount option to disable it.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]
reply other threads:[~2015-07-13 11:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=55A3A7DF.8080009@gmail.com \
--to=ahferroin7@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.