diff options
author | Darrick J. Wong <djwong@kernel.org> | 2022-04-11 22:49:42 +0200 |
---|---|---|
committer | Dave Chinner <david@fromorbit.com> | 2022-04-11 22:49:42 +0200 |
commit | 2229276c5283264b8c2241c1ed972bbb136cab22 (patch) | |
tree | 2b4a00c1b7be5c610b250ff7349fae960a17e955 /lib/dim | |
parent | xfs: recalculate free rt extents after log recovery (diff) | |
download | linux-2229276c5283264b8c2241c1ed972bbb136cab22.tar.xz linux-2229276c5283264b8c2241c1ed972bbb136cab22.zip |
xfs: use a separate frextents counter for rt extent reservations
As mentioned in the previous commit, the kernel misuses sb_frextents in
the incore mount to reflect both incore reservations made by running
transactions as well as the actual count of free rt extents on disk.
This results in the superblock being written to the log with an
underestimate of the number of rt extents that are marked free in the
rtbitmap.
Teaching XFS to recompute frextents after log recovery avoids
operational problems in the current mount, but it doesn't solve the
problem of us writing undercounted frextents which are then recovered by
an older kernel that doesn't have that fix.
Create an incore percpu counter to mirror the ondisk frextents. This
new counter will track transaction reservations and the only time we
will touch the incore super counter (i.e the one that gets logged) is
when those transactions commit updates to the rt bitmap. This is in
contrast to the lazysbcount counters (e.g. fdblocks), where we know that
log recovery will always fix any incorrect counter that we log.
As a bonus, we only take m_sb_lock at transaction commit time.
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
Diffstat (limited to 'lib/dim')
0 files changed, 0 insertions, 0 deletions