From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 6.8-rc5
Date: Wed, 14 Feb 2024 09:52:16 +0100 [thread overview]
Message-ID: <cover.1707900530.git.dsterba@suse.com> (raw)
Hi,
a few regular fixes and one fix for space reservation regression since
6.7 that users have been reporting.
Please pull, thanks.
- fix over-reservation of metadata chunks due to not keeping proper balance
between global block reserve and delayed refs reserve;
in practice this leaves behind empty metadata block groups, the workaround
is to reclaim them by using the '-musage=1' balance filter
- other space reservation fixes:
- do not delete unused block group if it may be used soon
- do not reserve space for checksums for NOCOW files
- fix extent map assertion failure when writing out free space inode
- reject encoded write if inode has nodatasum flag set
- fix chunk map leak when loading block group zone info
----------------------------------------------------------------
The following changes since commit e03ee2fe873eb68c1f9ba5112fee70303ebf9dfb:
btrfs: do not ASSERT() if the newly created subvolume already got read (2024-01-31 08:42:53 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.8-rc4-tag
for you to fetch changes up to 2f6397e448e689adf57e6788c90f913abd7e1af8:
btrfs: don't refill whole delayed refs block reserve when starting transaction (2024-02-13 18:39:09 +0100)
----------------------------------------------------------------
Filipe Manana (7):
btrfs: add and use helper to check if block group is used
btrfs: do not delete unused block group if it may be used soon
btrfs: add new unused block groups to the list of unused block groups
btrfs: don't reserve space for checksums when writing to nocow files
btrfs: reject encoded write if inode has nodatasum flag set
btrfs: zoned: fix chunk map leak when loading block group zone info
btrfs: don't refill whole delayed refs block reserve when starting transaction
Josef Bacik (1):
btrfs: don't drop extent_map for free space inode on write error
fs/btrfs/block-group.c | 80 +++++++++++++++++++++++++++++++++++++++++++++--
fs/btrfs/block-group.h | 7 +++++
fs/btrfs/delalloc-space.c | 29 +++++++++++------
fs/btrfs/inode.c | 26 +++++++++++++--
fs/btrfs/transaction.c | 38 ++--------------------
fs/btrfs/zoned.c | 1 +
6 files changed, 131 insertions(+), 50 deletions(-)
next reply other threads:[~2024-02-14 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 8:52 David Sterba [this message]
2024-02-15 0:12 ` [GIT PULL] Btrfs fixes for 6.8-rc5 pr-tracker-bot
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=cover.1707900530.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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