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+H93GTRKtOsFAmNsa3YACgkQ+H93GTRK
tOsJhQ//au/mROrD0TmJFv7hCPo7XgkgZDI8HZk6lQzR9NHeO+EKh16pgSKDqrB8
sXoXpKyp/zUrLd7jDhM545RpowTOYnUZR4RDMjz/jIWcFbfQMzqG/cxnYo2U5N3l
6LXsXBjZ7tK8cJTtKaj1xnazCPiGqRFN3OLJf1NdSdmTvRH+eQ9+NwO4iR/Ox6jB
L0vDDy+zNJLZ+p01ccwemMKPzd2jBOjjsWKdvIZc/9vhXYUfCfEFD9oDc3gNfy/6
vv3vurBEYTbjhF/EZ6CSsMMz+6n2zjHjOlvzuDY12XCvruK0kTywJDIrTC4MB5Z7
iHgEiRRM4b+Kc5nWSBktgQg5uv63XIfAQ9fffGQC/C1NHJyqdgtkhcK9ZK1yWJ6x
u+rvYQjvxiDlbC1xPXCkxTh4ANC7yEvVUO5IanMNFfcrnJSz9984NJxFjp2MvrLz
iOVYpenLn8Tcv8/zs2jj8B21qRxvsV788OozA/Uljs+OkqPm73hbWV+wySQQ5r/q
YTluhaV7heHCbe6OooXU4RlYUsUnB6PZwJKjWKdW4CQ1TTwyQIkpW0kfga6I1FEd
ZSaSLnWSNPC9pBmUbZpXybdSonmLTWqwJWRA0tjN3LjXCZCM4+dvhUUTomsLEM7n
KoW9+2F1zyjnHpG1lTI0vs+cUlMpVpLoBWSPRkfBwgxuwJ7rtdo=
=NjPj
-----END PGP SIGNATURE-----