From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v3 0/2] btrfs: trim enhancement to allow btrfs really trim block groups
Date: Wed, 29 Aug 2018 13:15:30 +0800 [thread overview]
Message-ID: <20180829051532.32005-1-wqu@suse.com> (raw)
This patchset can be fetched from github:
https://github.com/adam900710/linux/tree/trim_fix
Which is based on v4.19-rc1 tag.
This patchset introduces 2 enhancement, one to output better error
messages during trim, the other one is to ensure we could really trim
block groups if logical bytenr of block groups are beyond physical
device size.
These two patches are in the wild for a long time, and are pretty small
and the 2nd patch in facts fix a regression, and we already have test
case for it (btrfs/156).
Changelog:
v2:
Only report total number of errors and first errno to make it less
noisy.
Change message level from warning to debug
v3:
Rebase to v4.19-rc1.
Change back message level from debug to warning since it's less noisy
and will only report total failed bgs and devices.
Qu Wenruo (2):
btrfs: Enhance btrfs_trim_fs function to handle error better
btrfs: Ensure btrfs_trim_fs can trim the whole fs
fs/btrfs/extent-tree.c | 67 ++++++++++++++++++++++++++----------------
fs/btrfs/ioctl.c | 11 ++++---
2 files changed, 49 insertions(+), 29 deletions(-)
--
2.18.0
next reply other threads:[~2018-08-29 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 5:15 Qu Wenruo [this message]
2018-08-29 5:15 ` [PATCH v3 1/2] btrfs: Enhance btrfs_trim_fs function to handle error better Qu Wenruo
2018-08-29 13:43 ` Nikolay Borisov
2018-08-29 13:53 ` Qu Wenruo
2018-08-29 14:40 ` Nikolay Borisov
2018-09-10 18:42 ` David Sterba
2018-08-29 5:15 ` [PATCH v3 2/2] btrfs: Ensure btrfs_trim_fs can trim the whole fs Qu Wenruo
2018-08-29 14:24 ` Nikolay Borisov
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=20180829051532.32005-1-wqu@suse.com \
--to=wqu@suse.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).