summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorDave Chinner <david@fromorbit.com>2023-04-14 00:10:05 +0300
committerDave Chinner <dchinner@redhat.com>2023-04-14 00:10:05 +0300
commitf1121b995c9825f3267ad4f586b2ac644d87d5a8 (patch)
tree1e008972781984380c259e1f8a35fdf7637acb40 /tools/perf/scripts/python/export-to-postgresql.py
parente7cef2fe444b18e246d95d2a9156b37506590d61 (diff)
parentefc0845f5d3e253f7f46a60b66a94c3164d76ee3 (diff)
downloadlinux-f1121b995c9825f3267ad4f586b2ac644d87d5a8.tar.xz
Merge tag 'scrub-detect-inobt-gaps-6.4_2023-04-11' of git://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux into guilt/xfs-for-next
xfs: detect incorrect gaps in inode btree [v24.5] This series continues the corrections for a couple of problems I found in the inode btree scrubber. The first problem is that we don't directly check the inobt records have a direct correspondence with the finobt records, and vice versa. The second problem occurs on filesystems with sparse inode chunks -- the cross-referencing we do detects sparseness, but it doesn't actually check the consistency between the inobt hole records and the rmap data. Signed-off-by: Darrick J. Wong <djwong@kernel.org> Signed-off-by: Dave Chinner <david@fromorbit.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions