xfs: detect incorrect gaps in inode btree

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-----

iQIzBAABCgAdFiEEUzaAxoMeQq6m2jMV+H93GTRKtOsFAmNJ0h8ACgkQ+H93GTRK
tOvAGA/9GdxtfhUfpxSxE/N3fvUiRrifaIJHQwGPzMiIKzPMT9i8WyFDouvAsw1M
puFGrryzh0Bi6ct9X2SUi1gWEa10IkhAn+2cpc6MLr3e5HNRCeVyYQCyHjiZhH9H
jiUMw+qJAyqaYPeJOHRRoAIe2jQG6ES6zjwg11TwY7cvCnch6Vnsame6OKlGstKr
68/blZTrvYk3hbcEKQe7k6iiNRZq5JOifO0I6KTh3oVVRbPuFDz8icgH1NkxO1Uc
GYIwOI9yQbWC0E9f3eXn81XXUF5v9OM5fK9TwaYK60hLZ1tzlJqLH0zQ/kENvLkA
GcRTV5B0zTO87gt4bEjBRLL4gpWf9ZBHgTKm5nY10EMXbosoGhrU1krgcmDSYLHK
RO4ZqGf7uVcmr5huVMEFoJVmAMWHQu1YGIM5ijtQqU2FkbTdavyfN5b8y/oCA/SH
nZjk5fA8UCL/LWYC0u21c3yzmEn5FVXv5D5XeJLGsPfiEAtf+USCoi5I+VhQ3sO9
AeN6Y3LU9EvycmuboMihKHgYyDIUOwUfQqyaHKtfTNMO4Fka8PdRb4w0MG9CskOV
Xeajl8bu4YZUXhOc6LUJAufSs6XfURFg6V6tFKrsun1qkESO1BjNPY3ibMEXB7ak
YYxusqUxGqSPnw82kjP4nGQMM9ccMwHfSk4pbao+3gCj370OJqA=
=yeyS
-----END PGP SIGNATURE-----