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>
-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQQ2qTKExjcn+O1o2YRKO3ySh0YRpgUCZDdPbQAKCRBKO3ySh0YR
phQnAP40bvko8wtg11TJjhQAB+qYYn1YMopCN5b/IsAzbm5vagD/e3emRjHeEAvx
BKwA3OmE8JNC+gYr3fmp7RMQMHgekAY=
=5KnT
-----END PGP SIGNATURE-----